It now works for all container which implement std::size like C arrays.
Change-Id: I9ccf2c50b4e7518e44890b52686d5561358bcf8d
Reviewed-by: hjk <hjk@qt.io>
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
Amends 573f3e7185 which went in too early.
Change-Id: Ied93fd585aa26cb931f3acf13b55fbf7dbe0c163
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
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>
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>
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>
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>
The IncrementalDeployment::NotSupported was alwasy overridden with
Enabled or Disabled before actual action started, so it was not more
than a bool.
Change-Id: Ia4e986d08cdd10e20a741868ecb43e0c7ed4bf33
Reviewed-by: Jarek Kobus <jaroslaw.kobus@qt.io>
The border around the selection overlaps the line rect, so in order to
correctly repaint the selection when scrolling we need to widen the
prefiltering of painted selection.
Change-Id: I953749571e3e9ae412bf05f47ab3c4c3bfb8861e
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Added CMake support to the DAP engine in Qt Creator.
This feature can be enabled by setting the environment
variable QTC_USE_CMAKE_DEBUGGER. CMake debug session can
be started by clicking "Run CMake" or "Run".
Note:
Doesn't work with "Run debugging" in this patch.
Works only with cmake 3.27.0 and newer.
Change-Id: I756ea57f507aa4a6621ad62a8c0ef52c44a5185d
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: hjk <hjk@qt.io>
