The header file must be referenced relative to the location of the
source file.
Task-number: QTCREATORBUG-15599
Change-Id: Ib7d4aa5a62a94541cbe32cd340a8a1e7d6ef35e5
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Use Application instead of CppApplication as it's more suitable for Android
Apps.
Bump default C++ standard
Change-Id: I57cfafe24da42aeab5c46cb993cc371d6e71f0b7
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
We now get the resource path from creator. The -fPIC case is working now
too.
Change-Id: Id191e89e6d46706748d50440038a06a349972cc9
Reviewed-by: Ivan Donchevskii <ivan.donchevskii@qt.io>
Avoids configuring the Quick UI template always with the default
kit even if it does not match the minimum requirements.
Change-Id: I2a0d83346e53c2388c8c2ba41e9409fcb52beea8
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
This patch adds support for QmlFileSelector for
QmlProject and Qt Quick Designer.
Task-number: QDS-590
Change-Id: I0cc043d3ec9578008ec879b36fe834b70fb8c5ad
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
This setting is intended to derive file names from class names. It is
not relevant if the user explicitly provides a file name.
Fixes: QTCREATORBUG-14711
Change-Id: Ic31f8727220d99692286adf9ad0434ce06aa7c62
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
Some header like windows.h adds dangerous defines which are not used but
break the indexing like "small". We now preinclude them and undefine the
dangerous the defines. This can be used for speed up the indexing as we
could provide stripped headers.
Change-Id: I2a89a4719ada7591e0e7a1ecc411b2e0ffd40d9a
Reviewed-by: Ivan Donchevskii <ivan.donchevskii@qt.io>
Should help to drill down to individual expensive dumpers.
Change-Id: I983ba075231784f71dd9d5c3bda375a3ee508bf6
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
If a kit had no Qt configured the wizard for creating GTest projects
did not work even for build systems that did not need Qt (Qbs/CMake).
Json wizard needs some adaption before fixing this properly, so work
around this issue by specifying a common existing "feature".
Limiting the wizard for that case to desktop devices does no big
harm as the AutoTest plugin is currently limited to desktop anyhow.
Fixes: QTCREATORBUG-22264
Change-Id: I7a26f3cbc44762f7eda356128f6c25ca5cee6707
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
The other JSON based project wizards first show the respective "Project
Details" page, and the kits just before the summary. This makes sense,
make the Qt Widgets Application wizard consistent.
Change-Id: I8f91795498c6c5e432453b181fa11f0618080e3e
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Dialog allows you to save your gradients and to use stored presets,
including system gradients.
Change-Id: I6888446afd63c00f3cb8d9277d9e37517243491f
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
In fact, that color is not used in the non-flat classic theme. But
without it, the theme reader complains:
Theme "default.creatortheme" misses color setting for key
"FancyTabBarSelectedBackgroundColor".
Change-Id: I81462510150c1dc4fbb3d0bf5d7a2d610abb1f10
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
This change makes the combobox for the minimal Qt Version in the
"Scroll" Qt Quick Application Wizard visible.
In contrast to the other Qt Quick Application Wizards, the "Scroll"
variant had the minimal Qt version selection hidden. That was OK in the
initial wizard commit, where only one Qt Version would have been
selectable. But with the subsequent additions of Qt Versions in the
wizard.json, the combobox visibility should have been changed to true.
The consequence of the invisible combobox was that the default was
secretly selected. The default was Qt 5.10 for a while. But the default
changed recently with 52f95bae8b and
caused QTCREATORBUG-22245.
Task-number: QTCREATORBUG-22245
Change-Id: If4d2f384a28bf3dd130b097022ea6d8d30ef7509
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Change-Id: I9f932f1df93d723d5dc38bcee4f6ad6a4c653a7f
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: André Hartmann <aha_1980@gmx.de>
GDB 8.1 changed behavior when specifying breakpoints, it now tries
to pattern-match function names, hitting e.g. 'Foo::abort()' for
'b ::abort'.
While the API exposes a way to opt-out of the new behavior there's
no way to tell when to do that other than trial-and-error.
Task-number: QTBUG-73993
Change-Id: Ied2e640e65e40df6eac50117db890bd4b51d36ab
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
There have been apparently changes on the Qt Declarative side.
Task-number: QTCREATORBUG-22209
Change-Id: Ia9e387aa92465556b5b8aee3661e2fc063478f3d
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
Adding support for CMake as well as QMake
Task-number: QTCREATORBUG-17308
Change-Id: I615b58921918ec87f935e0f11d3dd23ec20f0ac1
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
This adds support for ShapeGradient in the property editor.
* LinearGradient
* RadialGradient
* ConicalGradient
Change-Id: I6a9cad3674b21174a12ac399cac88cb9dd972bd5
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
Editing finished is emitted, when we show an error dialog,
and the TextFiled looses focus. Even if the value did not change.
This triggers a second error dialog and hangs on macOS.
This is a regression from Qt 5.11 to Qt 5.12.x.
The workaround is to check for the value change manually.
Task-number: QDS-519
Change-Id: Ie8a3f342bc0b81941d07773d52947ad76ae27205
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
