Otherwise the warnings become too annoying, since they are
also triggered by undo/redo.
Do not disable the form editor in case of warnings.
Task-number: QTCREATORBUG-16306
Change-Id: Ieb1d6072269935e420e9cf988c900e1af792686f
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
We have to call registerDesignWidget() in extensionsInitialized()
and not delayedInitialize(), because the setup of Qt Creator is
already done when delayedInitialize() is called.
Because of this, if the original widget designer was disabled,
no design mode was available.
Change-Id: I8b02fcb10aa5305aff3c700f7831012ccf009b33
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
We have to ensure the modal dialog is actually visible
before calling process events later.
Task-number: QTCREATORBUG-16722
Change-Id: I4362a2887ee95483df082305b024232366eb074d
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
In pathological cases we might get event types without any calls.
Change-Id: Id5c9f02c95b60fe49a7cbbac511c3727ade71db0
Task-number: QTCREATORBUG-17885
Reviewed-by: hjk <hjk@qt.io>
The QML engine might (in the future) actually send the right message
to indicate a JavaScript null, that is:
{ type: "object", value: null }
This piece of JSON is then transformed into a QVariantMap. The QVariant
that signifies the null is unfortunately different across various Qt
versions. We can, however, detect it.
Change-Id: I3db42bb35a936bc02c749ab3a136b1d297aefdfe
Reviewed-by: hjk <hjk@qt.io>
Instead, get root project nodes directly from the project.
Change-Id: I5cf95a7dce1fa29c1adc26013ad03cc017f38a6d
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
Calling addPath() on the watcher could dead-lock on some operating
systems as we were in an asynchronous process.
Avoid calling addPath() from inside an asynchronous process and
perform this call from synchronous context.
Change-Id: I94cd401e12ccbb3526b8cc4232a9cff7ed552bbb
Reviewed-by: David Schulz <david.schulz@qt.io>
This patch reduces the former wizard to the test project part.
The wizard appeared more or less useless as there was no easy way
to add test cases later on and you normally do not need to have the
full skeleton of the project including a test sub project - except
when starting a TDD project.
Change-Id: I404d843b29f058876ea9696b7881f2e5e11b6af2
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
The fix is in 4.3
Task-number: QTCREATORBUG-17492
Change-Id: If155bd9b16a119e7b91161788708c21653222f8d
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Otherwise this can lead to infinite recursion. The android integration
reacts to kit changes by examining the available Qt versions and
creating additional android kits. This crashes, eventually. Also,
kitUpdated() is rather expensive, so we shouldn't call it if we don't
have to.
Change-Id: Ic5fe26f6b174c5b96a6ed8280bf744bf642863b2
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
With the old connection syntax the correct overload was explicit.
We listen to the original signal from QAction.
Change-Id: I0c8620148ebcb1ae0fceeefe54069c57c881423f
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
The existing logic works because the future watcher gets the canceled
signal even if the future was canceled before connecting the watcher and
starting the loop, and we schedule jobs before we start the loop and the
watcher gets the signal. But it is still better to avoid scheduling
anything at all in this case.
Change-Id: I3fa722bdd8391de7c7f3ba3fd8b1aaa65d9d2392
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
