When drilling into components we keep the context as an image
in the background.
Change-Id: I12c291ab1cff02d30f53f92ccd9a551a9dd63704
Reviewed-by: Qt CI Patch Build Bot <ci_patchbuild_bot@qt.io>
Reviewed-by: Henning Gründl <henning.gruendl@qt.io>
after switching to QmlDesigner and back.
Do not fiddle with the enabled state of the menus, they are managed
automatically by ActionContainer, depending on enabled state of the
actions they contain. Only enabling them in Design mode is the wrong
thing to do.
Amends 4642c5fd7d
Fixes: QTCREATORBUG-29268
Change-Id: I3c5704edf787f424f9a9e5e9cb363bbd410db3f2
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
When opening Qt Creator with clean settings, the run, debug and build
actions build be in the wrong state (enabled instead of disabled, no
debug icon).
This happened because a ProjectExplorer::updateActions call was removed
from the end of restoring the session at startup when moving the session
handling to Core plugin.
That updateActions call shouldn't be necesseray, and isn't if a session
is loaded, even if it is the "implicit default", because then
sessionLoaded(...) is emitted which results in the updateActions() call.
The sessionLoaded(...) signal was not sent if the file for the default
session does not exist. Fix that by also sending the signal even if no
file was actually loaded.
Amends cbeac777a6
Change-Id: Idb625253f29611e777d85f0feb6c196fae567ed0
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Similar to TypedAspect::operator()().
Task-number: QTCREATORBUG-29168
Change-Id: If8d5ad90e30e66309c4a4a06d9f96011efd00066
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
Get rid of RunWorker::appendMessageChunk().
Reuse postMessage() in RunWorker::appendMessage().
Reuse it also in ClangTool and RunControlPrivate::showError().
Change-Id: I719a97385e675e7ee3075fcd5343dbcaab68bef7
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: hjk <hjk@qt.io>
This allows creating the options page without having the
settings object already present, potentially delaying
its creation until its first truly necessary use.
Task-number: QTCREATORBUG-29167
Change-Id: I004fb19f0ea2b7e500747b3905283d74f749cd78
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
It was used in two places and other similar topics as Tutorials
did not have an icon.
Change-Id: I79c3502565958fd9f88889603d87ca1fab9d99e3
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
The line edit needs to be initialized with the stored arguments.
Fixes: QTCREATORBUG-29351
Change-Id: I9c4e0eed05a5c00520aebf1c6c4ea3cf17ef17df
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
If an iOS developer doesn't have a wildcard app identifier registered,
the app identifier must be in some sense "unique". So just
"my.example.com" creates issues in this situation.
Qt >= 6.1 tries to set a better bundle id, reading Xcode settings for
the last used prefix there, and Qt 6.4 improves on that in case this
Xcode setting is not available. So, try to use this mechanism in the
wizards.
Even with the automatic deduction of a bundle id, this might be
completely wrong (the Xcode setting is whatever was used last in a Xcode
wizard, regardless of target platform, it can be different for different
users, or for different teams that the user works in), and Qt doesn't
set it for macOS, so aside from out-of-the-box experience the user
should set an explicit bundle at some point.
So, keep the CMake property mentioned with a comment in any case.
Fixes: QTCREATORBUG-29340
Change-Id: I9dacae5c693ec2e23a9cf8bad660ad939303dbf3
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
Hide information about using features that were hidden in QDS.
Task-number: QTCREATORBUG-29361
Change-Id: I504634091c518d03d1d9e849205293bffc4955b3
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Amends 85ed23e639537d7f9e473c0fd3d016075433a225
Keep the hidden part, but the usage of "QTC_BUILD_PLUGINS" :
"$penv{QTC_BUILD_PLUGINS};Terminal" doesn't work because the parent
environment will be used and not the ancestor preset's environment.
Terminal will have to be enabled in the child presets via
`"BUILD_PLUGIN_TERMINAL": true` in the "cacheVariables" section.
Change-Id: I73c850a47d075a639810ed3aed5ceeb2e25b18de
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
By default hidden, so a user will have to have a `CMakeUserPresets.json`
file to inherit from it.
Changed `BUILD_PLUGINS` and `BUILD_EXECUTABLES` as environment variables
prefixed with `QTC_`. Qt Creator's CMake API will check these
environment variables.
Having them as environment variables allows a `CMakeUserPresets.json` to
expand the list like:
```
"environment" : {
"QTC_BUILD_PLUGINS" : "$penv{QTC_BUILD_PLUGINS};Terminal"
}
```
With `cacheVariables` this is not possible.
Task-number: QTCREATORBUG-29137
Change-Id: I925038d90806036abe4610e5c864b72d32960076
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
And add a template of CMakeUserPresets.json for
building on Windows platform in README.md
Fixes: QTCREATORBUG-29137
Change-Id: I359a9894e448acb1203de0c6acfc508e65655c03
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Show it as a "flashing" message instead
Fixes: QTCREATORBUG-29373
Change-Id: Ib9e7280a1b80cc52835aecb954f80e9daa80f7ca
Reviewed-by: Robert Löhning <robert.loehning@qt.io>
Qt Creator would do a compiler probe for CMake presets when the compiler
was not set.
But the same needs to be done when the generator is not set. Otherwise
Qt Creator would set a different generator by default. On Windows is
"Ninja".
This is different from what CMake does from command line.
Task-number: QTCREATORBUG-28693
Change-Id: I96e917b11561a042f9476bad302f3f153e37bafd
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
- Use \ingroup creator-tutorials to group tutorials
- Use \annotatedlist to automatically generate tables that list tutorials
- Add \brief commands to add descriptions to the tables
- Remove some leftover descriptions from the Qt Quick Application
wizard template docs
- Fix references to UI text
- Write "you" instead of "we"
- Use curly braces to define alt text for images
- Some language fixes
Task-number: QTCREATORBUG-28996
Change-Id: I4b611319b6867cae11d613e0a4d075923cdb037e
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Documentation mentions:
"Each may be either a string or an object" and "If no strategy field is
given, or if the field uses the string form rather than the object form,
the behavior is the same as 'set'"
Task-number: QTCREATORBUG-28693
Change-Id: Idd8cdffb94e9a943e0b133a63c628d9d8d54eb20
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Follows suite to 2cc4967 to have the user side code more uniform.
Most of the extra verbosity (setMacroExpander) can go away again
when distributing the expander via the "owning" AspectContainer.
Change-Id: I9e80cb235f0a4a9ebee601dd638aefbaa41efc1b
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
When the view is populated and sorted it gets its items
one by one. If multiple matches for opening an example are
possible we may end up using the wrong one which in turn
makes the test error out. So, wait for an expected amount
of items.
Change-Id: If6f6abfa757ede33311a8e617ab7d570df1240a4
Reviewed-by: Robert Löhning <robert.loehning@qt.io>
- Link the topics from "Show and hide sidebars"
- Hide "Working in Edit Mode" from QDS because the Edit mode is
hidden by default there
- Fix links to the new topics and remove links to
"Browsing Project Contents"
Task-number: QTCREATORBUG-29361
Change-Id: Ia9ae6474bf0925a76f9ccee693369d2460b9266f
Reviewed-by: Mats Honkamaa <mats.honkamaa@qt.io>
