...to decouple them from the sources used in other tests.
Change-Id: I80b3ea1478cdffdc28933e4320971f98a11d1898
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Add the following topics to the creator-tutorials group:
- Building and Running an Example
- Debugging a C++ Example Application
Task-number: QTCREATORBUG-29361
Change-Id: Ib6de92e99caf552ee8337b49af48bd04d6760474
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
And move the general information to the Overview (or the Code
view docs in the QDS Manual).
Task-number: QTCREATORBUG-29361
Change-Id: Ib1d13f3d81d707691c84aa4241ed28662e2bc8ee
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
There is no reason to limit the environment modifications to unique
variables. The environment modifications are processed sequentially
from top to bottom and there may modifications that are done on the
same variable (e.g. once a prepend, once an append,..)
Change-Id: I8a187737be1108e537a926239088c6352dc92957
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
- Pastecode.xyz has been replaced with DPaste.com
- The process has changed
Task-number: QTCREATORBUG-30209
Change-Id: I1c52923ada597bd741787a8c7ad66425ed5168f9
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
It mostly broke when Qt changed containers from int to qsizetype:
When we use QDataStream to serialize the value of `QList::indexOf`, but
deserialize that into an `int` variable, we don't get the same value
back.
Fix that, and also use begin/endMoveRows, which results in a better
selection behavior after dropping.
Fixes: QTCREATORBUG-30469
Change-Id: Ic99181ea7f75958766977ce7cf9d17c3d96103e2
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Right click on 3D view will now always clear selection if
there is no model under the cursor when click happens.
Fixes: QDS-12227
Change-Id: I922fc79472ced4a3aa5e518c03731edf240e1d43
Reviewed-by: Qt CI Patch Build Bot <ci_patchbuild_bot@qt.io>
Reviewed-by: Mahmoud Badri <mahmoud.badri@qt.io>
Previously the SettingsDialog did not call Aspect::cancel().
Without this, the volatile value is not reset if the user did some
changes before pressing cancel.
This "should" mean that re-opening the settings dialog should present
the changed values again. But since not all aspects are implemented
correctly, they reinitialize from their value instead of their
volatileValue.
When the Settings Dialog is reopened and applied, a warning is triggered
as the container thinks its dirty, but the Aspect::apply returns false.
Change-Id: I8fac66fc95f9118d69c789ced22481d121769f0b
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
It is not in the dialog described in the topic.
Change-Id: Ia0d1a399a2926e78cb8a0cc772abb7e2adc14840
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
And hide it from the top level TOC in the manual.
Link to "How To: Build with CMake" from CMake topics.
Task-number: QTCREATORBUG-29361
Change-Id: If0522cdd9636ac075e8bdeafa0fc7248199aaf2a
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Edit camera speed configuration consists of a slider and a multiplier,
which combine into the total camera speed.
Speed and multiplier are stored per scene.
Fixes: QDS-12187
Change-Id: I587c04cf80d1ca95b5a38c406158e46cdb91d06f
Reviewed-by: Qt CI Patch Build Bot <ci_patchbuild_bot@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Mahmoud Badri <mahmoud.badri@qt.io>
Makes it easier to reason in mixed setups.
Change-Id: I4f7aa43847dab51d4041fb1b9850ed9860a6dafc
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
This occasionally triggered crashes on static destruction when
hard-killing Qt Creator.
Giving QtVersionManagerImpl the plugin as QObject parent effectively
re-instates the lifetime behavior from before we moved to delayed
initialization. We keep the delayed initialization, at the (acceptable)
prize of a somewhat quirky setup.
Change-Id: I1b4be284a1b573325ed5cc441778eeb48b94c24b
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
It is important that the LicenseChecker's initialization (if that is
available) happens before QmlDesigner's, so add an optional dependency
to reflect that.
Add a PLUGIN_MANUAL_DEPENDS option to add_qtc_plugin, which explicitly
specifies the name, version and type. The existing PLUGIN_RECOMMENDS
requires the plugin target to exist to extract the plugin's version.
Change-Id: Ie2cf84e75964ce91ed8bbcdbeee9fa9770bed641
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
This changes the JDK download link to the JDK 17 packages on
adoptium.net, which is the latest source for JDK binaries for all three
host OSses.
Fixes: QTCREATORBUG-30335
Change-Id: I54322c82b7854d948fe15462f198f8eac1f58981
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
This got lost when replaced the default header implementation
with a customized one.
Change-Id: I5824b0e35a39746eb7056fbc95ea085505129f4e
Reviewed-by: Jarek Kobus <jaroslaw.kobus@qt.io>
If we use the same ID for the new kit as for the original, we get into
problems if the original kit re-appears.
This can happen when uninstalling a Qt version with the online
installer, and later re-installing it. Or when changing the install
settings path to a different online installation and back again via the
command line or the "Link with Qt" functionality.
Change-Id: Id99a3560ebed6264ad13dab5ff48945b30a8229f
Reviewed-by: hjk <hjk@qt.io>
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
... in a situation where no device is present. This happened to me
when trying to restore a "vanished" kit.
Change-Id: I7019385af115a5cd653b9a79e4420f1f8df4797d
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
While showing examples from remote Qt versions would probably be
possible, it is not a great idea performance-wise.
Task-number: QTCREATORBUG-30512
Change-Id: I2d00640bc8cbb3b19a89af1b17108e28604ef5a8
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
Disallow the unauthenticated access when the username doesn't
match the dashboard's username.
Change-Id: If4a38091b0bba42d89da911be45f823c248cc25f
Reviewed-by: Andreas Loth <andreas.loth@qt.io>
Reviewed-by: hjk <hjk@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Break the authorization process on any error coming from
unauthorized access trial except the UnauthenticatedException.
Call onUnauthorizedGroupDone only after successful execution
of dashboard's dtoRecipe(). Rename it to onUnauthorizedDashboard.
Change-Id: Ia7ce0f326c91722d0e68d5228cb46b94b47a7892
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Andreas Loth <andreas.loth@qt.io>
Reviewed-by: hjk <hjk@qt.io>
... and make sure to use notifyInferiorIll only in states
where the inferior might still be alive.
Change-Id: Ie002cd8b70cc610b15bab00554c027494a0ad2e3
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
I got a crash when clicking "Test" in the configuration of an
already existing ("Local Remote") device that was intentionally
not yet set up with working authorized keys after dismissing the
qtc-askpass dialog. The full reason is unclear, but this here
fixes it for me.
Change-Id: Ie07b89b85576beb59583370191e337fd1219db51
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
