so that it can be shared by more than 1 bundle. Also some relevant
tweaks.
Change-Id: I421648c26ac4a0d51612f21a5475f0938dfff331
Reviewed-by: Miikka Heikkinen <miikka.heikkinen@qt.io>
Reviewed-by: Qt CI Patch Build Bot <ci_patchbuild_bot@qt.io>
* Also the edit property of the StudioControls.CheckBox is removed,
because it might override the edit property of the item.
Fixes: QDS-12059
Change-Id: I2fe66061e2018cdbea44a51ffca2fb0e696d5bbc
Reviewed-by: Qt CI Patch Build Bot <ci_patchbuild_bot@qt.io>
Reviewed-by: Miikka Heikkinen <miikka.heikkinen@qt.io>
Reviewed-by: Mahmoud Badri <mahmoud.badri@qt.io>
If an editor area is hidden, for example by unchecking the "Editor" view
in Debug mode, this might hide the current view. This is ugly, because
opening an editor in that state either opens the editor in an invisible
view, or in case of Debug mode with hidden "Editor" view it switches to
Edit mode. Which is detrimental if the user has a separate editor window
open that could be used instead.
When an editor area is hidden, try to set a current view that is visible
(which might be the same as before).
Fixes: QTCREATORBUG-30408
Change-Id: I0eb65fddbc857b6efb12972b861b9f44204bd715
Reviewed-by: David Schulz <david.schulz@qt.io>
And remove the "GTK_THEME" hack
Even though Qt Creator now looked fine when started with a
light/mixed theme on a dark system theme, we still had to force
a light default palette on the application at startup.
The issue is that when the user switches the system theme
to dark during Qt Creator's runtime, Qt notices that and changes
the default application palette to dark.
Prevent that by setting a detached default palette on the
application on startup, even if we do not intend to apply custom
colors to it.
Task-number: QTCREATORBUG-28497
Change-Id: I7a43f108c2299967a14f382e52b62c31491e673d
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
The withCancel() method takes a function returning the sender
and its signal pair. When the signal is emitted, the queued
call to the running task tree is scheduled, and when dispatched
the *this group is canceled and the returned item finishes with an
error.
Change-Id: I898a7221d91a78225c73abc6885a18a2e7c2ae45
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
This used to not build on linux. Doesnt seem the case anymore.
Change-Id: Ia58d388bfe4f5cc794b29f8e25a9a8d6b3f229c3
Reviewed-by: Miikka Heikkinen <miikka.heikkinen@qt.io>
Reviewed-by: Qt CI Patch Build Bot <ci_patchbuild_bot@qt.io>
Successfully restoring auxiliary properties requires scene model to be
complete, so we must wait until model is attached.
Fixes: QDS-12615
Change-Id: I906e9b50df14fcdbc0cad8370c5466db5c1aab02
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
Mouse wheel no longer zooms 3D view when done in fly mode. Instead,
it adjusts the camera speed value.
Fixes: QDS-12291
Change-Id: I0bb5960d67cb25d545d3ac2ce2567c75f057ea72
Reviewed-by: Mahmoud Badri <mahmoud.badri@qt.io>
Reviewed-by: Qt CI Patch Build Bot <ci_patchbuild_bot@qt.io>
in sync with the current editor.
Before, we either tracked the current editor _or_ the current view if
there was no current editor. This made usage more complicated. Tracking
the current view in sync with a current editor makes setting these two
more complicated, but on the usage side are simpler. It also allows us
to just set the current view (which also sets the current editor to the
view's current editor), and to specifically signal changes of the current
view, and to keep a history of previous current views later.
Task-number: QTCREATORBUG-30408
Task-number: QTCREATORBUG-23654
Change-Id: I32967cea10972ca8b6939a84a0fbb396ca5c3721
Reviewed-by: David Schulz <david.schulz@qt.io>
When clicking on a mode button, the emission of `currentChanged` was
delayed by an event. That was supposedly to "improve the responsiveness"
of the mode bar, but I don't see any difference, and _if_ changing the
mode widget was a performance issue, this wouldn't be the right place to
fix or work around it.
The hack creates issues, because it separates the `currentAboutToChange`
and `currentChanged` signals by an event processing.
Amends bd2ba2307b
Change-Id: I53a7aa74fdcfb733a28574837ca9e95fc2e97f0b
Reviewed-by: David Schulz <david.schulz@qt.io>
after removing a bundle material from project
Fixes: QDS-12527
Change-Id: I72b4d99d15a6fbd454d45bdf0ba1a1b469e1a5bb
Reviewed-by: Qt CI Patch Build Bot <ci_patchbuild_bot@qt.io>
Reviewed-by: Miikka Heikkinen <miikka.heikkinen@qt.io>
If QtVersion::qtAbis() is called while the Android SDK is not yet set
up, AndroidQtVersion::detectQtAbis() returns an empty Abi list. After
the Android SDK setup, the Abi detection is repeated.
The recently introduced use of std::optional for Abis prevented that
"second chance" for Abis detection. After the Android SDK setup, Qt
Creator now had to first be restarted in order to have functioning
Android Qt Kits.
This change adds an Android specific hack in QtVersion::qtAbis() which
gives AndroidQtVersion a "second chance" to detect Qt Abis.
Amends: ee4f6ca1ae
Fixes: QTCREATORBUG-30568
Change-Id: I5d8a4fa7081d80015375c76305bb559d890b5f79
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
This allows setting _Preferences > Debugger > GDB > Additional Attach
Commands_ with the content:
process handle SIGSEGV --pass true --stop false --notify true
which results in the debugger not stopping in assembler for Java runtime
exceptions.
Task-number: QTCREATORBUG-29928
Change-Id: I8edf0d79dcccfe7ddb27502edb122fb5fb2c646c
Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
Reviewed-by: hjk <hjk@qt.io>
The old wizard syntax stopped working. Using QML file wizard as
template.
Task-number: QDS-12520
Change-Id: Ib188f898c28be8b7ad9284f431ef0526fbc7bf7e
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
Reviewed-by: Qt CI Patch Build Bot <ci_patchbuild_bot@qt.io>
There is now allExportedTypeNames which provides the same information.
Maybe we have to add more information to the modules like a flag for the
module type.
Change-Id: I1a8c0b33fc70a157d16a153102331447f370a032
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Qt CI Patch Build Bot <ci_patchbuild_bot@qt.io>
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
While in fly mode, Shift will speed up the WASD/QE movement by 100% and
Alt will slow it down 50%.
Also changed how shortcuts are disabled in fly mode. ShortcutOverride
events are now used to suppress conflicting shortcuts, which has the
advantage over old method as it will also suppress application global
shortcuts (such as Alt key moving focus to application menu).
Task-number: QDS-12291
Change-Id: I5c97d10b6f8955f3b3214e8e254a80cae7357ce5
Reviewed-by: Mahmoud Badri <mahmoud.badri@qt.io>
Reviewed-by: Qt CI Patch Build Bot <ci_patchbuild_bot@qt.io>
When any settings on the Build & Run -> General page changed, then
environmentId will be overwritted with Zero on settings save.
It cause probles with any project opening: on each QtC run will
be generated new environmentId that mismatch with environmentId in
the .user files. As result, any local settings drops and project
configuration starts from the scratch.
Change-Id: I05e36cdad99b7d5373c8f9ff418d68998b3fd893
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
