Alias task types manually.
Don't require the alias to be inside the Tasking namespace.
Addresses the 22th point of the jira ticket below.
Task-number: QTCREATORBUG-28741
Change-Id: I1bdda7fe5a01e4bcb5052ec328f4e0eace878651
Reviewed-by: hjk <hjk@qt.io>
The pattern is to use QT_[BEGIN/END]_NAMESPACE, instead of
QT_FORWARD_DECLARE_CLASS.
Change-Id: I9da39ee003e1d477a5f56980c218e275706bb3f4
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
It allows to set command/workingDir/env in one go.
Fix condition for setCommand() to match the one for setWorkingDir().
Change-Id: I0aa4639f3357c387a0fe8da321e94e34a3ea232d
Reviewed-by: hjk <hjk@qt.io>
targetAbi() is available in the base and non-virtual.
Change-Id: I1c65dccec98b7df5211b2ecfa1e91a4bb4b6e98f
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Move the burden of finding the shell of a device from the shell menu
to the TerminalWidget, so that opening the shell menu does not block
the ui.
Change-Id: I7f2e5a891f20faa53a1e3eec879866219f9bee0b
Reviewed-by: hjk <hjk@qt.io>
They have been added for future use for the cmake
build. Do so as well for qbs.
Change-Id: I0cb9bb161090a9c84e8c36567d6555bc0096b0e4
Reviewed-by: hjk <hjk@qt.io>
readSettings does not trigger signals when values change, so
other aspects that have setEnabler set will not realize that
the enablers changed and possibly not update.
Calling setEnabler after read settings ensures that the correct
value is used.
Change-Id: Ifff3ff13d9c78e16bddf8032b891a5004a035496
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: hjk <hjk@qt.io>
Otherwise, when the socket is a child of QTcpServer,
it may be deleted together with a server, while it's
still held in Parser instance.
Change-Id: I600e9cef1268ffc93e1e86d317e087df8b4d70cb
Reviewed-by: hjk <hjk@qt.io>
Apply it when process is started. This is a preparation
step before employing the task tree inside the ValgrindRunner.
Change-Id: I4cb64ef72b353af7ca97ae61fded23d9cea5e365
Reviewed-by: hjk <hjk@qt.io>
This one is used to represent an effect with its attributes while editing the current composition.
Also some refactoring to remove the composition properties from EffectNode.
Change-Id: Idd0137db98cb608f3ead49ba3208e4480a185e88
Reviewed-by: Mahmoud Badri <mahmoud.badri@qt.io>
Does not require early access to ICore::instance(), and there's
no point in attempting to save kits before they werde set up.
Change-Id: I68953c6019e14e88655ddb46b30ebb9f1916ec46
Reviewed-by: Jarek Kobus <jaroslaw.kobus@qt.io>
This was only meant as part of a safety net, but in the case that
the situation this was guarding against actually happens we'd also
notice by simply not seeing the effect. This is not different to
any other place in the code where we e.g. create objects/widgets/...
and don't put them in the right container.
Change-Id: I0700fd3ca235662b718cf01229211a4eebec8a9a
Reviewed-by: Jarek Kobus <jaroslaw.kobus@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
In KitManagerConfigWidget, plus a bit of style cleanup.
Change-Id: I6e28f697267c5e51d95a734cb2fe989346ac016b
Reviewed-by: David Schulz <david.schulz@qt.io>
