With e.g. the Extensions mode we add a mode that is probably not
interesting most of the times for most people. The only way to get rid
of modes currently is to disable the plugin that provides it.
Instead add the option to hide modes via the View > Modes menu. Modes
reappear if they are switched to (either via the short cut or other
means, like Debug mode when starting the debugger, or edit mode when
pressing escape often enough).
Change-Id: I56e20849a1f810aea9b5993b04892c915278845f
Reviewed-by: hjk <hjk@qt.io>
the same functionality can be achieved by handling the
QEvent::ReadOnlyChange type event in the TextEditorWidget.
Change-Id: I759c4bcac75e5d572f7a4656bc58c383b9fbc653
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Introduce operator&& and operator|| taking ExecutableItem
as a second arg.
Both tasks (first and second) execute in sequence.
AND:
- If the 1st task finishes with Error, the 2nd task is skipped
and the returned item reports Error.
- Otherwise, the 2nd task is executed
and the returned item reports the 2nd task's result.
OR:
- If the 1st task finishes with Success, the 2nd task is skipped
and the returned item reports Success.
- Otherwise, the 2nd task is executed
and the returned item reports the 2nd task's result.
Change-Id: Ib7874a82bd86eeb57fa5d3691b4a9e63a158772f
Reviewed-by: hjk <hjk@qt.io>
Introduce ExecutableItem operator!(const ExecutableItem &item).
This operator returns a copy of this executable item
with DoneResult tweaked by negation.
If this item reports DoneResult::Success, the returned item reports
DoneResult::Error.
If this item reports DoneResult::Error, the returned item reports
DoneResult::Success.
Change-Id: Ie609938e92bbc38ddcc66f5bc3244f864e3e59c7
Reviewed-by: hjk <hjk@qt.io>
Also de-Q_OBJECT-ify and drop two unnecessary casts.
Change-Id: I8113fc52e96226c3bdd72b36a904775c2fa5f1e6
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
This reduces the complexity of the beetle, which should make it better
recognizable in various pixel densities.
Change-Id: I1021e497366881847984e32e31c3523207f6498f
Reviewed-by: hjk <hjk@qt.io>
Move implementations either to the TextEditorWidget, TextDocument, or to
the caller side. This makes the TextDocumentManipulator basically a
repeater so we can easily replace it with a TextEditorWidget in the
next step.
Change-Id: I04de3cb295b56fbaae99145f8e579fe405b065a5
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
actions/upload-artifact@v4 complains if you try to override an existing
artifact.
Restrict only for one runner.
Change-Id: I0a8a8cd0fcdf34dc956de175eeb4c33b40ce1a8d
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Play icons usually are equiangular, i.e. not squeezed. This unsqeezes
the new play triangle.
Task-number: QTCREATORBUG-31080
Change-Id: I7243253255a015e78bf87bce273c2381dd96ee1b
Reviewed-by: hjk <hjk@qt.io>
There are two sources for examples: Qt versions directly, and "example
sets", which are just a tuple of display name, documentation path,
examples path.
The Qt installer registers an "example set" for Qt versions, so to avoid
duplicate entries we match Qt versions to example sets, if found. This
destroys any order the Qt versions might have been in before.
Order the results by Qt version (and other sets last) by first creating
all the items regardless of origin (noting their Qt version in the user
data), and sorting them before adding to the model.
Also use constants for the different user data fields.
Fixes: QTCREATORBUG-31108
Change-Id: I827be892a3abe17fa6afcd3c6f39bf225f7af494
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
The used QSysInfo::productType() provides various code/distribution
names which in some cases have little to do with the "host_os" that is
expected by the extension service API.
This change involves osTypeToString to instead return plain OS names.
Change-Id: I24b8070342c1de9de9040adcf5e06be967b6a180
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
Qt Creator will always use newer Windows SDKs, as we require at least
Windows 10 1809.
The define for TOO_OLD_WINSDK was done arbitrarily and broke
(LLVM-)MinGW builds.
Change-Id: If8e1fd4e0e3615bda23483877e67988ca04ea9f7
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
Basically the same. Only the type lookup of the inner type needs to be
avoided for performance reasons.
Change-Id: I2747ab44c23b764482b4a063d3618fae2e3c4d46
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
And remove the now unused DumperBase.Type.targetName helper function. We
can use the typeId nowadays for this. This reduces duplicated code and
simplifies adjustments in the base implementation without breaking the
cdbbridge.
Change-Id: If76297b83f088d98493c6f5aceea8fa93093e42e
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
... rather than just building them.
Fixes: QTCREATORBUG-27406
Change-Id: I5ddbb9ee4a05c6843bd78cf01746c57c6cacda3c
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
- Timeout can now be turned off and on
- Limit Files to Path Patterns adds filters for scanning
for tests
Task-number: QTCREATORBUG-30604
Change-Id: Ia0ab109c2dd2958804fea6f6faa1eb9a80377fe3
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Collecting relevant pieces in preparation of settings aspectification.
Change-Id: Ia221de3babf301f4f5d3583d346eeb9f91046aa4
Reviewed-by: Sami Shalayel <sami.shalayel@qt.io>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Where they were missing. The text is shown as a paragraph in the
extension manager.
Change-Id: I6e15c89fe4023b222e9c476f4312e13fcb0905c0
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Ctrl+C events are only handled properly for console applications. When
gdb debugs a GUI application the CTRL+C events are not handled. This can
be even reproduced with a plain gdb started from CMD.
This partially reverts commit 9d88da6c2b
and 670b4ec729.
Fixes: QTCREATORBUG-31131
Change-Id: I11c9d9dc08b4dbe450f38e27559b130dd317b675
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
A failed CMake run configuration could be the result of an compiler
update which then would cause CMake to fail.
Make sure to offer an upgrade path to the new Kit compiler values.
Change-Id: Ibabeb853259e23fe012d8b00e3d48979deee61a5
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Visual Studio is getting a fair number of updates. This involves also an
update of the Visual C++ toolchain.
This implies changing directory paths from "MSVC/14.39.33519" to "MSVC/
14.40.33807".
The linker "link.exe" is also stored in the same directory as the
compiler "cl.exe".
This commit makes sure that the linker also gets updated, not just the
compiler.
Change-Id: If8cd6e716604bc948ec8990921a14425ebcc7c30
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Do not apply the changes directly to the model, cache and then apply at
the right time.
Fixes: QTCREATORBUG-27005
Change-Id: Id099f21196900cd0e9787ac27887f2eec36f8045
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Qt SDK is setting "Ninja" as default generator, make sure to get a
working generator when CMake is newly registered as a default tool.
Fixes: QTCREATORBUG-31129
Change-Id: I6b93a8904696eedadec04c882495c644db7ddce7
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
