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>
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>
- use Utils::UniqueObjectPtr because it is a widget and
can get a parent which deletes it
- delete the DesignerPropertyMap as last, so there is no
connection to QmlEngine objects
- renamed view -> widget, where it was easy to rename it
Task-number: QDS-12480
Change-Id: I260909f2965f2943a9693b00876efcbb385d4259
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
The menu is created by QmlProjectManager, so it might not exist.
Change-Id: Ib37d9a2b19e02616c6564a55f153c48731dac0fe
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
There are situations where e.g. anti virus software leads to saving files
failing. Provide a way to disable atomic save for debugging purposes.
Task-number: QTCREATORBUG-30728
Change-Id: I1f3df009f89f6c27b2e0c9f91869b2a75f5575d8
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
Adding new nodes to the scene for some reason doesn't include them
to the full window render done for picking purposes. Changed the render
to be done via grabItem() on the target View3D instead, which seems to
work more reliably.
Fixes: QDS-12577
Change-Id: Ia5f01b9521fd898f8cf073f96d32fc31bf936a37
Reviewed-by: Mahmoud Badri <mahmoud.badri@qt.io>
Reviewed-by: Qt CI Patch Build Bot <ci_patchbuild_bot@qt.io>
Usually test frameworks or tools have their own timeout
handling or not at all.
Let the user decide whether to use a timeout or not.
This is a behavior change as now the test run does not
get automatically canceled anymore except when the user
explicitly enables this feature.
Fixes: QTCREATORBUG-30668
Change-Id: Ic5d98db0c52bfea092e427d317b12c41d6484ad0
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Reviewed-by: David Schulz <david.schulz@qt.io>
If the selected node is not View3D, check if the topmost item in
scenePosition is View3D and target that instead for "Edit in 3D View"
action.
Fixes: QDS-12347
Change-Id: I06b59f55246e828cced8dd3c15ee9b297e5edeb7
Reviewed-by: Qt CI Patch Build Bot <ci_patchbuild_bot@qt.io>
Reviewed-by: Mahmoud Badri <mahmoud.badri@qt.io>
Execution moved into a second thread. Progress dialog now shows a
distinct progress phase.
Change-Id: I933f823c9bfea562d9d3cee5d98990444073b4fe
Reviewed-by: Jarek Kobus <jaroslaw.kobus@qt.io>
