This saves time when developing Qt Quick applications, because
the QML files are interpreted at runtime. Therefore the
app does not need to be recompiled if only QML files changed.
Update the screenshot to make the Run button more visible.
Change-Id: I0ff2a1ca0fc24102e9c87b00896c387c18d0f1f1
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
If we cannot determine which executable to run we ask the
user to specify which run configuration to use, but if there
is only a single run configuration assume this one as
correct and just pick it up without asking the user
every time.
Task-number: QTCREATORBUG-19200
Change-Id: Ie45cf354b595bc666a595f51844ad2453655e0da
Reviewed-by: David Schulz <david.schulz@qt.io>
This saves some space in the tabs.
Change-Id: I968378de7d7a6331a41c79944ce910e23e63f2fd
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
Otherwise the run control will believe that the application is still
running.
Change-Id: I16ec9762362f526bd89eb21ceb82b89b295d7b5c
Reviewed-by: hjk <hjk@qt.io>
Keep the style responsibility add the widget. So coloring the
background with a helper widget is enough here.
Change-Id: I24bb82786e2a8ef4af01b9719d2bad4aa1997f1f
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
Currently structure "modeldata" contains numerous "data" elements.
It is hard to edit because one need to click on data element to check what's
the element "id" which corresponds to variable name in e.g. when model type
is ecmastript.
Change-Id: I47687627a71a46c21f172d4dc50df2c9b9359edd
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
The ShellCommand deletes itself if run asynchronously, and it also
cancels itself when ICore sends coreAboutToClose, so we must be prepared
for it to vanish at any time.
Task-number: QTCREATORBUG-19165
Change-Id: I6d6a737ea529012976a623f812f2c426518557fd
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
Effective functionality is unchanged, this only avoids warnings
about InferiorSetupRequested -> InferiorSetupRequested transitions
in the slave engine.
Change-Id: I727a271e105df69d18232854a7828960f40c0574
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
If a ModelNode is deleted we have to delete all related
frames.
Change-Id: I93f13f6a81c65d5cd858276baf754fd5a78d7b45
Reviewed-by: Knud Dollereder <knud.dollereder@qt.io>
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
This reverts most of 4977c915 and applies the same pattern for
setupEngine. Turns out that the removal was premature due
to the special needs of Android setup.
Task-number: QTCREATORBUG-19199
Change-Id: I4e2ff4f34a842f3296999a0651e7e8fd6470198c
Reviewed-by: Vikas Pachdha <vikas.pachdha@qt.io>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
When neither c++ nor qml debugging is enabled in the run page the
debugger wont start. Print a message to the Application Output pane
describing where the setting is located that enables debugging.
Change-Id: I580139e62c0fb0f4ae518ce818738165b80f8e0c
Reviewed-by: hjk <hjk@qt.io>
Because of QTBUG-3927 the tree views are scrolled completely to the left
when selecting any item because it makes the header column visible. That
is very annoying, because it makes items deep in the hierarchy hardly
readable, even if you manually scrolled horizontally to see them.
Scroll horizontally to make the actual item visible instead.
Task-number: QTCREATORBUG-19204
Change-Id: Ic083236feae8892d210b9d2b1238f3c6b80a8cea
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
Use QtOutputFormatter for CMake run configurations that belong to targets
with Qt configured.
Task-number: QTCREATORBUG-18586
Change-Id: Iedb6d7079649022b2ba6dabef37b79c0d33b8635
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
There are now wizards for creating apps that use Qt Quick 2
types or Qt Quick 2 controls (ScrollView, StackView, or SwipeView).
Some wizards generate ui.qml pages, while others don't. Therefore,
an include file can no longer be shared between the tutorials and
the creating projects topic.
Change-Id: If06e20511cb5f6fe9da28feff40cec0250a49416
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
This way we can pass it through signals across threads.
Change-Id: I6753233204d9210d181633e16f1d5bff967d55c9
Reviewed-by: Marco Benelli <marco.benelli@qt.io>
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Having the HelperWidgets next to the QtQuick directory was triggering
a bug in Qt (QTBUG-64237).
The property editor was white with Qt 5.10, because the "." import is
mapped to "./QtQuick" and was confused with QtQuick 2.x.
Task-number: QTCREATORBUG-19194
Change-Id: I4148d8e40f1e886eb41ffe6f4df62b213af5e9c3
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
Use QWidget method to block updates instead of an own implementation.
The QWidget grab resulted in crashes like in QTBUG-36600.
Change-Id: I4b57a0ba19e3a85e8e7985f893074364f5cb4490
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
The default property of most QtQuick items is data and
therefore "data" should not be used as a property name.
Task-number: QTCREATORBUG-19225
Change-Id: I54d1b72ce984debd4c366b7261e93b7a81b8c940
Reviewed-by: Marco Benelli <marco.benelli@qt.io>
Use the same qtc.projectexplorer. prefix for the gcc toolchains logging
category that is already used elsewhere in the ProjectExplorer plugin.
Change-Id: I5f2746504ed08d5422baaedd6860fa1ed3c86bae
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
In case the dynamic property was called "data" the designer
crashed.
There are still issues with dynamic properties called "data",
but it does not crash anymore.
Task-number: QTCREATORBUG-19224
Change-Id: I824a40729ed104f4eaa6a2bdc2fda336aafab836
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
