While it kind of works in principle it is very slow and therefore
practically not usable for real world projects.
Task-number: QTCREATORBUG-29585
Change-Id: Ia6357904e1ecc3e97adc77b49aa8ab7392f902c8
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
* Effects are items and we have to use __effect/source and allEffects
to idenfify them and get the correct bounding rectangle.
* For now we use a custom parser to work around issues when editig the model
Change-Id: I78690498c44f8285d3bb6ce78eafcafb9c26b2f1
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
The joinable thread was under the locked mutex. So the sleep notifier
could not arrive.
Change-Id: I548c89904b09f8dcc02cb7ae0486880f519915d2
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
Threads are still considered joinable after their execution. So sleeping
thread have to be joinded first. Add test
Fixes: QDS-12308
Change-Id: Ie01588293e3b7ce9fe149d52a25ba03d174cca88
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
Qt Design Studio uses a specific Qt Runtime version to
run the projects. This update include the Qt runtime
versions used for QDS 4.5 releases in the document.
Fixes: QDS-12201
Change-Id: I90bf2c952bef70840af382f03bc0ae47b43e3a0d
Reviewed-by: Mats Honkamaa <mats.honkamaa@qt.io>
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
Reviewed-by: Qt CI Patch Build Bot <ci_patchbuild_bot@qt.io>
* Add QTC_CHECK for crash
* ActionAreas should not be "garbage" collected if they have no target.
* Initial ActionAreas do not have a target and ActionAreas without target make sense to a user. We do not want to delete them together with the target.
Task-number: QDS-12181
Change-Id: Ie520c47aad990a8ff07fc3346e6772226d334ce5
Reviewed-by: Marco Bubke <marco.bubke@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Color properties set with hex color values display a
color tool tip, but named colors failed for Qt6 while
it was still working with Qt5.
Change-Id: I6457bbdc86dd7f036bc48dc40cfa16cda570b95f
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Sami Shalayel <sami.shalayel@qt.io>
- Added a topic on how to make a camera follow an object
- Some minor fixes to the Cameras topic
Fixes: QDS-11700
Change-Id: Ieafa9c57d5649d3de6f823cc907734ab6f24091d
Reviewed-by: Qt CI Patch Build Bot <ci_patchbuild_bot@qt.io>
Reviewed-by: Johanna Vanhatapio <johanna.vanhatapio@qt.io>
- Add the case where you cannot see your new QML module.
- Remove obsolete use case and message.
Task-number: QTCREATORBUG-29826
Change-Id: I29c2852d32007c64e343bcbe30a1d218f9ff89d3
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
This reverts commit 16c12f71ff.
Reason for revert: Introduces bugs.
AndroidQtVersion::addToEnvironment() set varying ANDROID_NDK_PLATFORM
values in successive calls. Only after a call of
QtVersion::ensureMkSpecParsed, a consistent value is set.
The symptom could be fixed by adding QtVersion::ensureMkSpecParsed calls
in strategic places (e.g. in the beginning of
AndroidQtVersion::addToEnvironment), but it does not make me confident
that this covers all potential code paths. The change that introduces
the issue is 16c12f71ff and will therefore
be reverted. It may be resurrected in QtC 14, but with much caution.
This issue seems to be specific to qmake. It hardens my impression, that
there are no easy gains to be made in the current state of the Android
plugin. An improvement for one use-case will break another use-case
which may be fixed only after two release cycles. It is Mikado code:
"Only touch if needed and safe".
Change-Id: I6ad860f6af8848a900d9421837a03929f9a57645
Fixes: QTCREATORBUG-30554
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: David Schulz <david.schulz@qt.io>
- Fix a link
- Add Reference categories
- Move Version Control Systems up in the TOC
Change-Id: I6b6f9562c581ce8b78503d7e70ce132a0e9253a7
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: David Schulz <david.schulz@qt.io>
QC nowadays provides lldb on Windows which gets automatically
registered.
Beside this correct expectations for the compiler based on the
LLVM path that had been used for building the QC package and
might be the same on the machine the test runs on.
Change-Id: Ie9553b79bb0eb0012386bd71422005c184638046
Reviewed-by: Robert Löhning <robert.loehning@qt.io>
* Dialogs will be closed after model changes
* Some menus and dialogs moved for improving the performance issues
Fixes: QDS-12057
Change-Id: Ie298732ec1d3c9e4623663cd539abfa1b119ff98
Reviewed-by: Mahmoud Badri <mahmoud.badri@qt.io>
- Cell text color now matches that of the column name.
Task-number: QDS-12168
Change-Id: Ia3e53a448c57e2f76347e83076271944936f6c05
Reviewed-by: Mahmoud Badri <mahmoud.badri@qt.io>
Reviewed-by: Qt CI Patch Build Bot <ci_patchbuild_bot@qt.io>
The outlines of the numbers from 8 through 10 were blurry when
copy-pasted.
Task-number: QTCREATORBUG-30209
Change-Id: I2db64931fb8f16567a8890b1aa6d91f80defc573
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: David Schulz <david.schulz@qt.io>
Check if qmlls is enabled before showing tooltips from the QtC's code
model. This way, other hoverhandlers, like the one used for language
servers, have the possibility to show their tooltip.
Task-number: QTCREATORBUG-29826
Change-Id: I5d879c7d4c04a27bc668e8900f54984788b02727
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Use an elapsed timer in the syntax highlighter to periodically return
from the highlight and push a continue highlight to the end of the event
loop.
This allows the user to interact with the editor in between those
batches. If the user modifies the document in between highlighting
batches, the area that still needs a rehighlight is increased if needed.
This also reverts 62ea85ee6a and the
related changes.
Task-number: QTCREATORBUG-28727
Change-Id: I7c394dbdff658330bb72f3b68b9928980947db75
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
If the linked project is not the top level project our
path mappings did not work.
Try to get the correct file path by using QC internal
find functionality.
This helps for opening files by activating issues inside
the issues table or when clicking links of the issue
details.
Unfortunately this does not help for the inline
annotations or respective marks.
Change-Id: Ie34e1b20ff8b1b2b37e9f04c1d41bc2a4c33f260
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Avoid having none of the buttons selected which looks
confusing.
Change-Id: I445c4da970c4dfbd8a35228e31092c788d0b5d37
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
