Change-Id: I2d858ed2cd90f8e4297114cc47502b5a8d57f638
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>

Change-Id: I97f73ff82e4aac6af7f6b8d04364339ba484910a
Reviewed-by: Marco Bubke <marco.bubke@digia.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>

Change-Id: I50a74778f5fa0895110f2157728b9d99b677a6c5
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@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>

Change-Id: I3b47a82b64932dc42bc2948ce4a2e8e290fc0324
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>

Change-Id: I3a2e433157c65deb6ca85c8128046ce535ec59be
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>

Change-Id: I4dddf19d37004f59bfbe75b45e0b626bf1563fa2
Reviewed-by: Kai Koehne <kai.koehne@digia.com>

Change-Id: Ib40cf370798e12540d81e2f7ec532bb119293e4e
Reviewed-by: Kai Koehne <kai.koehne@digia.com>

Change-Id: Ie9d1535ae93ca0a28bf7f6ccd3ee73bcb783be4c
Reviewed-by: Daniel Teske <daniel.teske@digia.com>

Apparently, that define is only needed for qmake, if at all.

Change-Id: I12b6768760deddc2a780da105f33857eec6e8710
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>

Change-Id: I3bab4c2749ef87058015ead3218c5dc6c14bee98
Reviewed-by: Marco Bubke <marco.bubke@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>

Task-number: QTCREATORBUG-10167

Change-Id: I0bf3d28ba2837cdbfa4f5a38148ee00fe2b1c897
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

Task-number: QTCREATORBUG-10166

Change-Id: If57b0c95487bcfe2c11c25a847d26c0746c379b2
Reviewed-by: David Schulz <david.schulz@digia.com>

Task-Number: QTCREATORBUG-10039

Change-Id: I8a6b80d18da1be0697bd8aaceb5d8670105a8f49
Reviewed-by: Mehdi Fekari <mfekari@blackberry.com>
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
Reviewed-by: David Kaspar <dkaspar@blackberry.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>

Change-Id: I85eac02934cd5f7f2f4664b9642c55bb3a23aa1e
Reviewed-by: Marco Bubke <marco.bubke@digia.com>

Change-Id: I7e0a6d457aa26748758b6402955c81eae2c94782
Reviewed-by: hjk <hjk121@nokiamail.com>
Reviewed-by: Daniel Teske <daniel.teske@digia.com>

We can expect people with Qt 5.1 to also have QtQuick.

Change-Id: I84b0323c6ea11b46f3ee41c0bbdc5f059643f208
Reviewed-by: hjk <hjk121@nokiamail.com>

Commit cf56178d introduced an impressive amount of syntax errors.

Change-Id: Ibaf8b8384b06ee92b658b71f08ac8d14e92c19b0
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
Reviewed-by: Joerg Bornemann <joerg.bornemann@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>

Change-Id: Ie30c0409cb2288c8c2cf649a92e7b54aa9481cb2
Reviewed-by: Marco Bubke <marco.bubke@digia.com>

This can be used to check if reparenting makes sense.

Change-Id: Ide1146841be76d8979dc452954fc6965ecdfef3d
Reviewed-by: Marco Bubke <marco.bubke@digia.com>

Updated class names and functions. Fixed imports.

Change-Id: I5f12e3a108a0e60c091acc9c415ff77e52118029
Reviewed-by: Kai Koehne <kai.koehne@digia.com>

Change-Id: Idb327a9ecefe5a4b55e9f0f47edfec30ae634289
Reviewed-by: Daniel Teske <daniel.teske@digia.com>

This patch ports our Qt Quick views to Qt Quick 2.

Change-Id: Ie0cfd81e7ebb76d2ed667211ad063feaaff5aa14
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>

This ports the welcome screen to use QtQuick 2.0.
I have disabled the plugin on Qt4 builds.

Change-Id: Ia921d0747c8f7d4441c88fc9fb77b822496091f4
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>

Modified CMake plugin to work correctly with RemoteLinux plugin.
Because of not being able to extract files to be installed from CMake
project, only executable targets are automatically added to deployment
files. All other files have to be specified in CMakeDeployment.txt file
which should be placed into root of CMake project. The file format is:
> deployment/prefix
> relative/source/file1:relative/destination/dir1
> ...
> relative/source/filen:relative/destination/dirn

Where:
- deployment/prefix is (absolute) path prefix to which files will be
  deployed on the remote machine.
- relative/source/file is file path relative to CMake project root.
  Plain files - no directories or wildcards supported.
- relative/destination/dir is destination directory path relative to
  deployment/prefix.

Change-Id: I0831636c1b9aac3ff16bb6293104c512d2abfb5a
Reviewed-by: Daniel Teske <daniel.teske@digia.com>

The one test for which we included it does not need it anymore,
and the StringUtils test fails to link on Windows when it is present,
so remove it again.

Change-Id: Iebe810c82842047a323f65722a61940271f921f3
Reviewed-by: Orgad Shaneh <orgads@gmail.com>

They did not build on Windows.

Change-Id: I0c688b8e1b78e9bb06e2efd6e2cbf8791f272bc2
Reviewed-by: Orgad Shaneh <orgads@gmail.com>

While this was great two years ago it seems to backfire with
some of the recent gdb builds.

Change-Id: I63ed1e225edeb0e59f079a5e9b5b8c92f3031c7d
Reviewed-by: hjk <hjk121@nokiamail.com>

There was a typo in ad58c2bb that caused
incorrect result of the check.

Change-Id: Ie4e6dca08892eb19d9e0e66c5252670865d17144
Reviewed-by: hjk <hjk121@nokiamail.com>

QMessageBox apparently only saves the state in the actual
QMessageBox instance ... anyhow, it's the only place in
QtCreator where we use QMessageBox, which makes it look
somewhat alien. Instead, use CheckableMessageBox and
extend it for an information dialog.

Task-number: QTCREATORBUG-9876

Change-Id: I8014e972943dd4a336952325ebb9f6cbc5dd0902
Reviewed-by: hjk <hjk121@nokiamail.com>