There was more stuff broken by the switch to Qt Quick 2 than were
originally noticed, and the original fix was buggy as well.
Change-Id: I2b3e0619af923c52aba809355ac271b67097adf1
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
Search in visual mode should select text up to matched position.
Using commands should work with search movement; e.g. 'd2/needle<CR>'.
Commands should be also properly canceled if search movement fails.
Change-Id: Ic695dccaf3f36ccae2f2b1a93f888d5ba9805a78
Reviewed-by: hjk <hjk121@nokiamail.com>
These ASSERTS have no fatal consequences (data losss, guaranteed crash).
Therefore we can use QTC_ASSERT instead.
Change-Id: Ia155f23d06f41432ba7504459816f000d4fe8f11
Reviewed-by: hjk <hjk121@nokiamail.com>
Otherwise the widget is created but never inserted in the widget
hierarchy, if the designer was never activated.
In this case the widget was not deleted.
Task-number: QTCREATORBUG-10169
Change-Id: Ic86d540a7044c07e272357edafd4d2f81fd1b7a4
Reviewed-by: Marco Bubke <marco.bubke@digia.com>
If you hover over a tab the content will be visulized as non editable.
Change-Id: If7fcc8aaa319e0f952f501f6e9e2fc767b89b636
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
To give the impression that the content is non editable.
Change-Id: I1869d02a27b2d1a7c2c12abb9a8d8d24068adf22
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
... for the same function
Task-number: QTCREATORBUG-5748
Change-Id: Iadf5be76c24f95cf057c2112a8248bea2a9e20cf
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
Apparently, that define is only needed for qmake, if at all.
Change-Id: I12b6768760deddc2a780da105f33857eec6e8710
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
If detached from rewriter do not parse directories.
Change-Id: Ie07e732d5e09b337d43221df4aa88c7e62aac55b
Reviewed-by: Marco Bubke <marco.bubke@digia.com>
ResolveExpression now correctly handles wide and
UTF-n string literals.
Change-Id: Ide2373ffdc4c9e1e4b53236a8e2782653d15e687
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
Presumably this function is currently const because no current
implementation actually changes device properties, but there
is no reason why that should not be allowed.
Change-Id: I80e4355be70e40bca9df5e1287a1d1d3f60c6534
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
Make the id of the kitinformation the config widget is configuring
accessible from the widget.
Change-Id: I15af2cfc18ab2ba012d43c3c6b71ee0011f994ad
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
Refactor the code of the build configuration factories. The idea is to
generalize the code so much that we can allow plugins to install
custom build configuration factories for the platforms they support.
To support this use case the following changes where done here:
* BuildInfo class was introduced to describe one build configuration that
can be created by a factory.
* Factories report a list of BuildInfo to describe what they can produce.
This fixes the need for factories to implicitly create one buildconfiguration
and then create another one 'officially' to support debug and release build
configurations to be set up for projects.
* Do no longer work around factories to create build configurations.
Change-Id: Ic372e4a9b5c582633b467d130538948472b89d91
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
We check for defaultPropertyIsComponent() and the metaInfo has to be valid.
Change-Id: I957c8440facec0ba54e527f2eda40926c5637b31
Reviewed-by: Marco Bubke <marco.bubke@digia.com>
An item is not considered a container if the default property is
a component.
Change-Id: I73453fb17d6c181cdd79cd6620307e5c30cac09d
Reviewed-by: Marco Bubke <marco.bubke@digia.com>
