GitLab

Do not warn if no device is set at all: No device is a valid value,
no reason to warn about that.

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

Change-Id: Ib81a3ca1bef70250e83dcf5f45bc145ff78cee32
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>

Change-Id: I68052cc83ffb1dac79b571990d85bcc3e17d6fb3
Reviewed-by: Eike Ziller <eike.ziller@digia.com>

The device status is updated only when it is connected or disconnected.
Thus a restored device would mantain the unknown state in which the user
cannot remove the device.
Using always the disconnected state so the use can remove the devices.

Change-Id: Icdeb1e314eef0e5b1553decfc728e4b9eab939ab
Reviewed-by: Christian Kandeler <christian.kandeler@digia.com>

Change-Id: Ia67d98855548c4d2c80ad76ff633a2399e30ad9c
Reviewed-by: Ulf Hermann <ulf.hermann@digia.com>
Reviewed-by: Kai Koehne <kai.koehne@digia.com>

Change-Id: I5da7f2971dfd957d0188149eb8b4fde198609e6b
Reviewed-by: Ulf Hermann <ulf.hermann@digia.com>
Reviewed-by: Kai Koehne <kai.koehne@digia.com>

For example in the projects mode

Task-number: QTCREATORBUG-10917
Change-Id: Ic6bcc10f9794451101d56b1871b37768641bac35
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
Reviewed-by: Erik Verbruggen <erik.verbruggen@digia.com>

Task-number: QTCREATORBUG-10942
Change-Id: I5c46212dda2228c72378e9ba1ad076be8945add1
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>

Change-Id: Idafe728642e8c0c0637b8793e912178fdc011aa0
Reviewed-by: Fawzi Mohamed <fawzi.mohamed@digia.com>

This reverts commit 96ecfb9e4a500837e048cf29a89fe52d31ec1db9

device changes at the moment do not trigger projectexplorer's slotUpdateRunActions so this reduces the usability if one starts out without device.

Change-Id: I9fc4ba14ce45d5000d0a8af5c06e0ca9b3080d86
Reviewed-by: Fawzi Mohamed <fawzi.mohamed@digia.com>

The version of MobileDevice.framework shipped with iTunes 11.1.3 and
XCode 5.0.2 does not support concurrent connections well, asking
for the application path while the connection to gdb was open would
lock up the device, and require a reboot.

Task-number: QTCREATORBUG-10922
Change-Id: I939cb9e75896e200da552d6708c01e726b9d7b45
Reviewed-by: Fawzi Mohamed <fawzi.mohamed@digia.com>

Task-number: QTCREATORBUG-10670
Change-Id: I23b553984b2c1848983299613004cbd910dc92dc
Reviewed-by: Fawzi Mohamed <fawzi.mohamed@digia.com>

iosdeploystep did call reportFinished on the future interface.
This is incorrect, the finished signal should be emitted instead
This lead to a reuse of the future  due to missing call to
buildStepFinishedAsync which lead to failing on the second run of
the deploy step.

Change-Id: I96b8874bc98c77453d5c0af96c818dff6e955167
Reviewed-by: Fawzi Mohamed <fawzi.mohamed@digia.com>

This makes it easier to brush over harmless platform output differences
like the '4u' vs '4ul' in the std::array test

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

When using autocrlf, warnings
"LF will be replaced by CRLF in ..."
occur, causing the command window to pop up, which is not
desired.

Change-Id: I399080a98f9386dbbaff2c90c6d4ba4877d08057
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>

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

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

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

Change-Id: Iffb7e667098050ceb38eab40d4ed7850bf3bea94
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>

For easier diff

Change-Id: I34effdc85c4bef51b80f5763e1522162c2b64b4e
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>

Step 1

Change-Id: I1416df4e152be231be386209ca1f360be31c58c6
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>

Needed for easier diff for upcoming refactoring...

Change-Id: I779b25d09a03fc1ed54e2ba35946678a5e863265
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>

Task-number: QTCREATORBUG-10911
Change-Id: If564db41df106334bc6909b99f37f468b5f07720
Reviewed-by: Kai Koehne <kai.koehne@digia.com>

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

Task-number: QTCREATORBUG-10917
Change-Id: If151da45a83ce5b7ddf3166c16f8c63783f53f6a
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>

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

Preprocessor variables __LINE__,__FILE__,__TIME__,__DATE__ where destroying
the following systems when affected variables were standing  within the
same line with those variables:
* highlighting
* refactoring
* local renaming

Task-number: QTCREATORBUG-8036
Change-Id: I1a4b919d15812872ca5a8e63b1031ec1ab144c22
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>

!!! Revert again ASAP !!!

Task-number: QTBUG-35143
Change-Id: I9eb724f07c7b6b49a7df0be4e1d4c76dac206af5
Reviewed-by: Eike Ziller <eike.ziller@digia.com>

"Deploying an Application on Mac OS X" has been renamed
to "Qt for Mac OS X - Deployment".

Change-Id: Idea88e83dd6ea6fd2e25fd4093c2e2cd27f632f7
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>

This causes trouble with the unit tests on windows.

This reverts commit 0fe28d652f1219978d23030cbb322d09ada5a68f

Change-Id: I08d4991d9b86ee8b80d093899f2e33e2be1c1565
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>

Change-Id: I871a5079dcef6712c3d7ddb21dbfab4c6f7c8f88
Reviewed-by: Robert Loehning <robert.loehning@digia.com>

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

This will need to be replaced with the results of the import scan, but
that will be for 3.1.

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

We should not have to list all supported version of Qt Quick here.
This also fixes adding states for Qt Quick 2.2.

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

Task-number: QTCREATORBUG-20

Change-Id: If6349605e1f396e88c8e3e008328fc2cac8a4119
Reviewed-by: hjk <hjk121@nokiamail.com>
Reviewed-by: Przemyslaw Gorszkowski <pgorszkowski@gmail.com>
Reviewed-by: Erik Verbruggen <erik.verbruggen@digia.com>

Change-Id: I6f6982b2e07bb1277d805ce48160afb25f33c7ae
Reviewed-by: Erik Verbruggen <erik.verbruggen@digia.com>

The MoveDeclarationOutOfIf quick fix modified a IfStatementAST in case
there were several such ASTs in interface->path(). The resulting AST was
invalid (else_statement was pointing to 'this' afterwards), thus the
afterwards executed PointerDeclarationFormatter (an ASTVisitor) was not
able to finish his visit.

The actual problem was that op->pattern in the match() calls was not
reset.

Task-number: QTCREATORBUG-10919
Change-Id: Ifbcac73e75690321ef45b6d8c2dc32fcea236efa
Reviewed-by: Erik Verbruggen <erik.verbruggen@digia.com>

Change-Id: I519428496c3139a0ff97ab28d291853eca19887d
Reviewed-by: Erik Verbruggen <erik.verbruggen@digia.com>

Change-Id: I40f27c7b542f512de78ea2e7fa6e777b652edc4a
Reviewed-by: Christian Stenger <christian.stenger@digia.com>

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