* Introduce a proxy class for thread synchronization
* Use signals for appending text to output window
Change-Id: Iecbb010e6b6e9dab27d9862a43dafa450f2bb1f8
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
These are not build system issues and deserve their own category.
This has the side effect of avoiding them to get cleared when e.g.
reparsing Qbs files.
Change-Id: Ib949504533f7f15a560796bea91cae329f19a20b
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
Example: 'LATIN SMALL LETTER DZ' (U+01F3) is rendered as "dz".
The uppercase of that is 'LATIN CAPITAL LETTER DZ' (U+01F1), or "DZ".
The titlecase is 'LATIN CAPITAL LETTER D WITH SMALL LETTER Z' (U+01F2) "Dz",
which is what I would expect here when capitilizing the first letter.
Change-Id: If4fe342e310168dd6190034d4f1ceca4c2ef4a1a
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
Provide a QProcess-like abstraction that can be used
to implement processes running locally or on a remote
device. Objects of a concrete class implementing the functionality
are created by IDevice objects.
Current implementations are:
- Local execution (QProcess-based), provided via the DesktopDevice.
- Remote execution via SSH.
- A specialized case of the former for remote Linux systems (provided by
LinuxDevice).
The latter is already being used in a number of places. As a result, lots of
code dealing with details such as setting the remote environment could be
moved to a central location. These things are no longer the concern of whoever
is wishing to run a remote process.
Change-Id: I919260ee6e77a020ca47226a4a534e7b8398106f
Reviewed-by: hjk <hjk121@nokiamail.com>
The soft links inside the framework can't be resolved.
Change-Id: I9f328bc074091236fb33eee63e725e49efeac5c9
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
Widget margins has been zeroed so the default margins of
the 'Type Specific' group applies only. Request and Upload buttons
has been placed on a separate row to allow better width stretching.
Task-number: QTCREATORBUG-9981
Change-Id: I86d3be06d0057e92289fe6ed5cf38f16f5f3158b
Reviewed-by: Christian Kandeler <christian.kandeler@digia.com>
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
Reviewed-by: David Kaspar <dkaspar@blackberry.com>
Don't show them in the project tree and don't tell the codemodel that it
needs to update itself. Not the cleanest code.
Task-number: QTCREATORBUG-9957
Change-Id: I37fc1e2d401f59365ffbbb53617eeb7b86eb6456
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
Otherwise there's no way to have a '%' in a file after replacement.
Task-number: QTCREATORBUG-9793
Change-Id: I3c9bfac9f3bd8a19bbc293839d9d69ccf951e264
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
This cleans up various bits of the avd support in Creator.
- Adds a abi combobox to the create avd dialog.
- Moves the startAvd code into a separate thread, so that
starting a avd while deploying doesn't block creator anymore.
- Implements a better waitForAvd function that works even
if a emulator is already running and accurately can
detect that it has finished booting.
Note: There are still many problems in the avd support in creator.
- The "clean libs on device" and "install qasi" functionality block
the gui thread if they are run on a avd.
- If no avd exists and no suitable hardware is attached, the user gets
a create Avd dialog, which doesn't tell him why he needs to create a
avd. That information is hidden in the compile output.
Still this fixes the main use case of hitting run on a newly created
project with no actual device attached.
Change-Id: I76b3fdb1bdf3eadac07f82ad7d145ce6af453326
Reviewed-by: BogDan Vatra <bogdan@kde.org>
prefixNames containing white spaces did crash.
This was lost during refactoring.
Instead of calling toLower one the string
we call toLower only on the first char.
This creates camel case ids.
Change-Id: I1093d12258e87d4f56ceef67a553d844afdfd376
Reviewed-by: Marco Bubke <marco.bubke@digia.com>
A non-existing command may not always result in a "FailedToStart" error,
but can also lead to "normal" finish with a non-zero exit code (from the
shell), which means that people whose remote system is missing the "env"
command currently get no feedback at all when pressing the "Fetch"
button. (Independent of this, the exit code should always be checked
anyway.)
Change-Id: I1387897436825c18e7df2d03d5ee3870ff6b70f5
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
We assing a DWORD to wParam when posting WM_DESTROY,
thus we can be sure that there's no loss of data.
Change-Id: I21c9b658ff06ea7792d0a357ff508bdab04fa5f7
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
Make methods static and add a instance() method for Signals/Slots.
Remove ProjectExplorerPlugin::taskHub() method and use the new
ones instead.
Change-Id: Ifae24ff19579fc524cbd61bddc826095c443adfa
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
Reviewed-by: hjk <hjk121@nokiamail.com>
For cross compile suggestedMkspecList is always empty,
so dont try to autodetect a compiler then if toolchain
was already found.
Change-Id: I97d70e65fef3a5be0fdf20949c18cf98d51513d4
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
