We use a value of 200, which is also GCC's default.
Fixes: QTCREATORBUG-28770
Change-Id: Id02b324cd2ffa81a709441a5d93856bcd06501c3
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
..when expanding variables and macros.
Fixes the plugin unit test on Windows.
Fixes: QTCREATORBUG-28744
Change-Id: I8a047854d6d43e901b01b10660e29b7d6544d0b7
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
During API review, it was decided (and implemented) that REQUIRES is the
better/more descriptive keyword than MIN_VERSION.
Change Creator's wizard accordingly.
Change-Id: I831cdc956204b1e379c3815104698d3f881abf6c
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
When editing e.g. CMAKE_PREFIX_PATH in the initial configuration
settings it was resolving the path(s) in there, thinking that it was
relative to the project directory.
Fix that after editing the resolved file path was set as the new value,
instead of the raw unexpanded data.
Fixes: QTCREATORBUG-28779
Change-Id: I14d097e3a3a51b78006dd30a67b08477cfe0f2d8
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
The wrong Tr::tr could be executed by code indirectly including a *tr.h
file from another module.
To Translate in a header file, use QCoreApplication::tr().
Change-Id: I30e67245991d2c2f0eeb01ab356555bdb9841af0
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
4.8 was released end of 2018 and the setting is not critical.
Change-Id: I02856e98303debd3a1adc28d49b28c5d728ad553
Reviewed-by: Jarek Kobus <jaroslaw.kobus@qt.io>
Align with the rest.
Change-Id: I48ac1cae738b909d90fd123128c1959f3635278e
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
This is now in line with the other menu buttons in the editor toolbar
like the language client button or the python interpreter and repl
buttons.
Change-Id: If22d3e9c87274eee2fefe8e30f6b0648be5d60c9
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
For references to the module-own context, use Tr::tr().
For references to other modules, use the right context name (with "::"
prefix).
Change-Id: I6dce8f1ceccb23c44d93f1826402cd3be8e98e5a
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Move the .toString() uses into DeploymentData::addFilesFromDeploymentFile
Change-Id: Ic9ef22da1918ca105c92f0231960dab27b0d80bb
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
The file name is not supposed to be the button label.
Fixes: QTCREATORBUG-28746
Change-Id: I45ee2a860da8f7ffefc6d72c0d85b7f6a261489c
Reviewed-by: David Schulz <david.schulz@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
It adds an indirect dipendency to QmlCompilerPrivate too. We stick to Qt
6.5 because the private API changed.
Task-number: QDS-9049
Change-Id: Icb0b406fc47759763384e167c0cabbffc1c9e186
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
It removes the workaround in QmlProjectRunConfiguration.
Task-number: QDS-8915
Change-Id: I319cdf976980b616eb28cabb40dd63416d7e27fa
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
When an import option conditionally depends on another option that
depends on a third option, toggling the third option needs to change
the enabled state of the first option controls as well as the second
option controls.
For example, consider this set of options (actual case with options
for generating mesh levels of detail in Qt 6.5):
optA
optB, enabled when optA is true
optC, enabled when optB is true
optD, enabled when optB is true
If optA is false, optC and optD controls need to be disabled even if
optB is true, because of the chained conditions.
Fixes: QDS-9055
Change-Id: I10aeb7596cf9c8a9053c7d08ec9ebb7a46db2cd2
Reviewed-by: Mahmoud Badri <mahmoud.badri@qt.io>
Building CXX object src/plugins/qmlde...dir/components/componentcore/designericons.cpp.o
/data/dev/creator-out/src/plugins/qmldesigner/components/componentcore/designericons.cpp:84:21: warning: ‘const QStringList& {anonymous}::iconFontMandatoryKeys()’ defined but not used [-Wunused-function]
84 | const QStringList & iconFontMandatoryKeys()
| ^~~~~~~~~~~~~~~~~~~~~
Change-Id: I978d6a52cf4030fe07352d6ee89c2db3d0433c05
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
..and debug under cursor for QtTest and GTest.
Depending on the information coming from the code model
we may be able to get a correct scope even when standing
inside the function that is defining the test.
This makes more sense than the original behavior which
made it a hard requirement to stand on a literal to
run or debug a test under cursor.
But as the codemodel does not provide usable information
for all frameworks keep the original behavior as fallback.
Task-number: QTCREATORBUG-28752
Change-Id: I13ea7b0ad1e8207da6cb884d212667c4c657957c
Reviewed-by: David Schulz <david.schulz@qt.io>
