- 01 Apr, 2014 14 commits
-
-
Daniel Teske authored
The workflow for adding a library for multiple archs is not ideal, but now a little better. The user has to go to the deploy setting for a kit per architecture and add the right extra library. Change-Id: I2bda6961f6f1164bdc58acd78fa3d2221977f0cf Reviewed-by:
Oswald Buddenhagen <oswald.buddenhagen@digia.com>
-
hjk authored
Change-Id: Ic28cff5962b03e0a30c9c67526027b3e2799e738 Reviewed-by:
Christian Stenger <christian.stenger@digia.com>
-
Christian Kandeler authored
Change-Id: I5cd40bd819c799838cde82a60037bbe3762e166d Reviewed-by:
Joerg Bornemann <joerg.bornemann@digia.com>
-
hjk authored
Change-Id: I12b31a41e55855ae99989e350075871a2dad4ef6 Reviewed-by:
Christian Stenger <christian.stenger@digia.com>
-
Joerg Bornemann authored
Task-number: QTCREATORBUG-11928 Change-Id: I86ae446e01e3c1c7fe53df886428437f3eda7c18 Reviewed-by:
Friedemann Kleint <Friedemann.Kleint@digia.com>
-
Leena Miettinen authored
The tutorials that were based on the Addressbook and Battery Status examples have been removed from the manual. Change-Id: I3eb55e40d652205d66ebe9e901736d1971809186 Reviewed-by:
Eike Ziller <eike.ziller@digia.com>
-
Leena Miettinen authored
Change-Id: I4d026e4b6d7ce73f3e10860cc29e7c4090a5287f Reviewed-by:
Eike Ziller <eike.ziller@digia.com>
-
Leena Miettinen authored
Rename as "Creating a Mobile Application". Add the steps necessary for deploying to iOS devices. Fix the link in the Tutorials tab in the Welcome mode. Change-Id: Ie72bf087c789d8d1299b9b5ac19ad732da534012 Reviewed-by:
Venugopal Shivashankar <venugopal.shivashankar@digia.com> Reviewed-by:
Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
-
Eike Ziller authored
Change-Id: I796d981e9b19a54d9ef9ef735d0f72d9ad0b1d34
-
hjk authored
Change-Id: I359cbdcfb0594b988e041c06efa44c6fd85a8d65 Reviewed-by:
Christian Stenger <christian.stenger@digia.com>
-
Marco Bubke authored
Task-number: QTCREATORBUG-11786 Change-Id: Idabd190f3bd8f02ebcc24e4f6be27ca8784d283f Reviewed-by:
Thomas Hartmann <Thomas.Hartmann@digia.com>
-
Christian Stenger authored
Change-Id: I287ce12a040a81a6392f39385c5a0c26d53b8e28 Reviewed-by:
Robert Loehning <robert.loehning@digia.com>
-
Orgad Shaneh authored
Change-Id: I6cdea03f2ebe372dfcd758f927a4adbcf3f96f60 Reviewed-by:
Eike Ziller <eike.ziller@digia.com> Reviewed-by:
Leena Miettinen <riitta-leena.miettinen@digia.com>
-
Marco Bubke authored
Task-number: QTCREATORBUG-11900 Change-Id: I009e620a19a1747ea7a1c3580c63e0a56b05564e Reviewed-by:
Alessandro Portale <alessandro.portale@digia.com>
-
- 31 Mar, 2014 26 commits
-
-
Orgad Shaneh authored
Change-Id: I6405c4dfa07eba1ea09ba23fe20667769eaca748 Reviewed-by:
Nikolai Kosjar <nikolai.kosjar@digia.com>
-
Friedemann Kleint authored
Change-Id: I4ce52075140220c70ef3d25df1321454a01a0c0f Reviewed-by:
Robert Loehning <robert.loehning@digia.com> Reviewed-by:
Christian Stenger <christian.stenger@digia.com>
-
Christian Kandeler authored
Change-Id: I337af64834388ef643108d8502be0abcf53cd9c6 Reviewed-by:
Fawzi Mohamed <fawzi.mohamed@digia.com>
-
Fawzi Mohamed authored
Change-Id: I09657cbfb50a8dfeeb4122c920b24926684a1680 Reviewed-by:
Fawzi Mohamed <fawzi.mohamed@digia.com>
-
Kai Koehne authored
When QML language debugging hasn't been set to a fixed state yet by the user try to find a qmake step to decide whether to enable QML debugging by default or not. This is a hack, breaking the separation between qt build steps and debugger run settings. However, adding a generic project infrastructure for this specific use case is probably overkill... Task-number: QTCREATORBUG-11474 Change-Id: Ib65c8474b9b7ec187769c209531ff56bc8293cde Reviewed-by:
Aurindam Jana <aurindam.jana@digia.com> Reviewed-by:
Eike Ziller <eike.ziller@digia.com> Reviewed-by:
Alessandro Portale <alessandro.portale@digia.com>
-
Kai Koehne authored
Use the same check as in the DebuggerRunConfigurationAspect to decide whether to enable qml debugging, or not. This allows us to follow the qmakestep setting in the run settings in a follow-up change. Task-number: QTCREATORBUG-11474 Change-Id: I67900cf719a56c0246e792c6aca66ce8e5d77daf Reviewed-by:
Eike Ziller <eike.ziller@digia.com> Reviewed-by:
Alessandro Portale <alessandro.portale@digia.com>
-
Daniel Teske authored
Task-number: QTCREATORBUG-3959 Change-Id: Icba8cabe573557356aa634bb162367ce5b8bd582 Reviewed-by:
Nikolai Kosjar <nikolai.kosjar@digia.com>
-
Fawzi Mohamed authored
Change-Id: I6dbea675a77ed0d151dc6bbdcfa501c00107998c Reviewed-by:
Fawzi Mohamed <fawzi.mohamed@digia.com>
-
Fawzi Mohamed authored
We now update after the profile has parsed, not when it is changed. Change-Id: I70bf9bed85c77677d0ece0d7b99dff590a9e4d47 Reviewed-by:
Fawzi Mohamed <fawzi.mohamed@digia.com>
-
Kai Koehne authored
Fixes a regression in 07f7dd9c that caused the Qt SDK installer to complain e.g. with Toolchain x86-linux-generic-elf-86bit does not exist. Qt Creator has code to automatically detect toolchains, so it's not necessary for every toolchain to be explicitly registered. Task-number: QTBUG-37875 Change-Id: I1e8909da2ff919a8cccdf86bb3a2f7a5cc79a257 Reviewed-by:
Tobias Hunger <tobias.hunger@digia.com>
-
El Mehdi Fekari authored
Change-Id: I96ca087e3174d9631a24cd6f752547c75c0dc024 Reviewed-by:
Leena Miettinen <riitta-leena.miettinen@digia.com> Reviewed-by:
David Kaspar <dkaspar@blackberry.com>
-
Fawzi Mohamed authored
Change-Id: I54bcbd7f2142ab95618005f1f108a122bfe18d32 Reviewed-by:
Fawzi Mohamed <fawzi.mohamed@digia.com>
-
Eike Ziller authored
Change-Id: I90405eaba68efa0f6861a54a7283dc062a3d1408 Reviewed-by:
Leena Miettinen <riitta-leena.miettinen@digia.com>
-
Tobias Hunger authored
The mingw Qt versions need to know the mingw toolchains to run qmake since that may link to a library provided by mingw. This patch delays loading of the Qt versions till after the Tool Chains are available by explicitly listening to the toolChainsLoaded signal of the Toolchain Manager. I do not see how else we can enforce the proper ordering with the plugin initialization scheme we have. Task-number: QTCREATORBUG-11898 Change-Id: I5a93c2b2b32c658695017295652242a5aaa6ee60 Reviewed-by:
Daniel Teske <daniel.teske@digia.com> Reviewed-by:
Tobias Hunger <tobias.hunger@digia.com>
-
Fawzi Mohamed authored
Change-Id: Ief267e7fda5c8329cb77ab6104d4ec71a409f979 Reviewed-by:
Fawzi Mohamed <fawzi.mohamed@digia.com>
-
Fawzi Mohamed authored
Change-Id: Id0e877a88bf4bafb44c4be655838253210bcefb3 Reviewed-by:
Fawzi Mohamed <fawzi.mohamed@digia.com>
-
David Kaspar authored
Task-number: QTCREATORBUG-11793 Change-Id: I882c43580ced2601bcc2176b27adc32de88df1b2 Reviewed-by:
Mehdi Fekari <mfekari@blackberry.com> Reviewed-by:
Tobias Hunger <tobias.hunger@digia.com> Reviewed-by:
David Kaspar <dkaspar@blackberry.com>
-
Eike Ziller authored
That makes it more visible, which is especially important when we show example sets that do not come from a Qt version there. Change-Id: Ib99955e70abb95053d9e8cd718ab599153e6eaaf Reviewed-by:
Kai Koehne <kai.koehne@digia.com> Reviewed-by:
Eike Ziller <eike.ziller@digia.com>
-
Eike Ziller authored
Added with setting "Help/InstalledExamples" which is a string list, each string is a triple of (display name, manifest parse path, examples path), joined with '|'. If a documentationPath for a Qt version is already added through the InstalledExamples setting, we do not show an extra combo box item for it. That makes it possible for an installer to register a single example set for the same Qt version in different variants (e.g. iOS, Android x86, Android arm) Change-Id: I42dd8f9ca9cb6cee247e3dc8ce9d014e56852e79 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Tobias Hunger authored
Change-Id: I59de95d2d2e72b676df50ede6c9d3c6182b38892 Reviewed-by:
Tobias Hunger <tobias.hunger@digia.com>
-
Ulf Hermann authored
As most of the numbers involved are single precision floats rounding errors can easily lead to such numbers. Instead of ignoring it set the range to the smallest allowable value. Task-number: QTCREATORBUG-11879 Change-Id: If8d08b27cc9e4cf2a63ff4973f519b0d3363178d Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
This is insignificant at lower zoom levels but becomes really annoying when closer to the 500ns limit. Task-number: QTCREATORBUG-11879 Change-Id: Ide0069f7c6b135aa31262a4396559fa3ba89f8e3 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
When zooming in the x offset and width of events can be larger than 2^31. We can restrict them to the visible area, though. Task-number: QTCREATORBUG-11879 Change-Id: I841300b55cdd583d5c3fa58b196101038f6f6036 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
Change-Id: I80abc136237917c259fe63b05f783ad1c7601469 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
This prevents some overflows when zooming into the timeline. Task-number: QTCREATORBUG-11879 Change-Id: I968c4737af8c64798d196a1463268d86146864e7 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
Ulf Hermann authored
This function is by a large margin the most often called one when loading a trace. Passing it as a pointer to qSort certainly doesn't help. Also, qSort is deprecated. Task-number: QTCREATORBUG-11823 Change-Id: I98d744d1615733de93a8d35bccaa338643a2f6f4 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-