Qt Creator offers to install them if it finds the NPM package
manager on the computer.
Task-number: QTCREATORBUG-30209
Change-Id: I2ab147dfae6a639b2b9f21acabd6f4d2ec339ac6
Reviewed-by: David Schulz <david.schulz@qt.io>
This limits the number of signals being sent.
Change-Id: Ie4b0661571a9d1bbd5708e33e21e0911e7a9fcbd
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Github and others turn `[^footnote]` into anchor links to the next
occurrence of `[^footnote]: Description`.
Task-number: QTCREATORBUG-30119
Change-Id: Ieebcad8ef58ccd8c7faa6aa83a165ce3f7ea1a01
Reviewed-by: David Schulz <david.schulz@qt.io>
Plan is to hide the plugin class definition to the .cpp later.
Change-Id: I27f6d2dd23adb4f3ab47d99b0626956889d2750f
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
In this way we don't construct a giant recipe
(~7000 tasks for Creator project) but simply repeat
the task execution many times.
Change-Id: I06758e2afa721f73e28adb42e6fccee0f955e01f
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
The current code updates the application icon for every task added to
the progressmanager. There are cases were we add a lot of tasks in one
go, for example when receiving diagnostics from the code model. This
might not even change the application icon (since it only updates for
errors), but we never the less create a new icon and send it to the os.
Optimization 1: Only trigger an update if the text differs from the
previous icon detail text.
Optimization 2: Do not directly update the icon but start a timer to
collect multiple updates and update the icon when the event loop is re-
entered.
This only affects Windows and Mac since the progressmanager_x11
implementation does not update the application icon.
Change-Id: I80cbb6f2520a83e79e2dba1b4079ab77fb7bf453
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
It enables the access to the internal TaskTree.
Emitted by TaskTreeRunner::start(), after the task tree
is instantiated and before it is started.
The lifetime of the passed task tree is controlled by the
TaskTreeRunner and is limited to the one particular execution.
Don't store pointer to the passed task tree.
If unvoidable, store the QPointer instead.
It may be used e.g. for connecting to the TaskProgress.
Change-Id: If0af11eb136c9cbff2e4c6e91f8b18a114880f74
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: hjk <hjk@qt.io>
This addresses the 30th point in the bugreport below.
Task-number: QTCREATORBUG-28741
Change-Id: Ifa157311b3aae413b19075d36e11c75e6066881d
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: hjk <hjk@qt.io>
If a task or task's adapter sends done() signal directly
from the destructor (which isn't really desired),
ensure we disconnect from this signal beforehand,
otherwise this may start invoking normal handling of task done()
and interfere with the destruction.
Fix NetworkQuery d'tor.
Add a test for it.
Add some TODO items.
Fixes: QTCREATORBUG-30204
Change-Id: I56a34d0f00c961c15bd1bcffef45520a4be5bce0
Reviewed-by: hjk <hjk@qt.io>
For devices that that supports. The goal is that iostool will be
unneeded in the end for these.
Call `devicectl device install app` with the right device id and bundle
path and parse its output.
This doesn't use our custom provisioning check, but relies solely on the
errors that are returned by devicectl.
Task-number: QTCREATORBUG-29682
Change-Id: Ibae0908841004a12e1fc91b154bedea4b37db053
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
To the IosDevice. So other parts of the code know if the device can (and
should) be handled via devicectl instead of iostool.
Change-Id: I700bd1528fad505c3f4b6442d73e24b09ceba68a
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
In Preferences > Devices > Devices > Type Specific.
This makes it fit the style of other devices, and automatically makes it
possible to select and copy text from it.
Change-Id: I637858a939ada261504970611ffdb7eccf003c1c
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
Queue the call to start() so that it's executed after the nested
event loop is started, otherwise it fails on Windows with QProcessImpl.
Fixes: QTCREATORBUG-30066
Change-Id: Ibb17ef0f668f52c05b26a521e18c94e637992ba5
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
When a number of repeats is known in advance,
make the progress reporting aware of it.
Add a test for it.
Change-Id: I676a4aa9eb469cfe40a2729d231c706dff3ca07c
Reviewed-by: Jarek Kobus <jaroslaw.kobus@qt.io>
Let it have its way of partially rewriting the document.
Change-Id: I4ea3d6a5ae271356fe111bd5f5e9591d0f75b532
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
If the number of iterations is known in advance it may
help in calculation of total task numbers for progress
reporting purposes.
Change-Id: Ie36de67a4f3271820aca539afe0816974773a152
Reviewed-by: hjk <hjk@qt.io>
