This is to avoid confusion with generic Label
Quick component.
Change-Id: I6a72266c394862706215b6db40bcd3592f9d24b3
Reviewed-by: Ulf Hermann <ulf.hermann@digia.com>
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
Avoid rendering outside of the canvas by forcing the windows
size onto the scene, and also removing the related candidateSize
logic.
In the QtQUick1 based profiler one could scroll the canvas also
vertically, but that doesn't work any more. This is a hot fix
to work around the problem, we can hopefully bring back the
full solution later ...
Change-Id: Ibd3d54f6b98c3764e104116d395a77b880d88bcb
Reviewed-by: Ulf Hermann <ulf.hermann@digia.com>
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
Do the QML based painting when requested inside the UI thread, and
only copy the final canvas pixmap in the renderer thread (in paint()).
To avoid excessive re-drawing delay the painting via a timer to the
next event loop run.
The previous logic was still from Qt Quick 1 times, where the paint()
method was called in the GUI thread. This has changed in Qt Quick 2:
Here the paint() method will be called (on Unix) in a separate renderer
thread, making the drawRegion / onDrawRegion connections implicitly
deferred.
Change-Id: I298547013658e4cd1e94115305577bdb96cd0b2a
Reviewed-by: Ulf Hermann <ulf.hermann@digia.com>
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
QnxUtils::qnxEnvironmentFromNdkFile() function was parsing the content
of the bbndk-env.sh/bat script file to resolve environment for BB10 tools.
The content of the script file is not documented and is a subject
of heavy and frequent changes.
Now QnxUtils::qnxEnvironmentFromNdkFile() function executes the script file
and dumps the important env. variables that are parsed standard way.
Change-Id: Ie7636054d62ec62b32cd3ab3d93a59b7d6c0882a
Reviewed-by: Tobias Nätterlund <tobias.naetterlund@kdab.com>
Reviewed-by: Nicolas Arnaud-Cormos <nicolas@kdab.com>
This information looks a bit out of place on the
landing page where we make a distinction between
Qt Designer and Qt Qt Quick Designer.
Change-Id: Ie8b7cb678c1ecc293f74bc43252536b550649b88
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
This patch should go to 3.0
This reverts commit aa624b9defb205acf10b535f7bbb187e5a52785c
Change-Id: I5efed4110275d25b5bf21d8894de441e5f715dbe
Reviewed-by: Aurindam Jana <aurindam.jana@digia.com>
This is to avoid confusion with generic Label
Quick component.
Change-Id: I6a72266c394862706215b6db40bcd3592f9d24b3
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
The display options like "Use debugging helpers", "Dereference Pointers"
etc are already updated the moment they change while the debugger is
running, but it was missing the initialization at startup.
Change-Id: Id39a38c6646c3c19819e2c122d7f8be285eae09e
Reviewed-by: hjk <hjk121@nokiamail.com>
There's no target if the project is in the parsing without configuration
state.
Change-Id: Id21e2ded5b634253267e956accc27715e6562941
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
The case looks like this:
Two kits on the targetsetuppage.
- Already existing kit, selected
- Temporary kit not selected
Switch reset() and setupProject() to the order they had before
the TargetSetupPage generalization.
Task-number: QTCREATORBUG-10417
Change-Id: I51cfb1e01193c57e06aebeaa8defa11809e24c50
Reviewed-by: Mitch Curtis <mitch.curtis@digia.com>
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
No longer use the undocumented __X86_64 macro to decide on the
word width of a tool chain target. Use __SIZEOF_SIZE_T__ instead.
That is documented to be set and should also be applicable outside
of the intel x86 world.
Some versions of mingw do not define __X86_64 on 64bit intel
machines and thus are not properly detected.
Update unit tests that try to guess the ABI to use the new macro
instead and fix the fallout.
Side effect: Some abis are detected in a different sequence now.
That should not change the tool chains though as the ABI that is actually
used is stored extra and does not referrence that list.
Task-number: QTCREATORBUG-10584
Change-Id: Ia9e5909cdff3b057ef74b24c0f2d654a14253c21
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
The previous approach when debugging on pure QNX 6.5
no longer works with QNX version >6.5. Use proper way with
"set nto-executable" and "run" instead.
Change-Id: I00961236b416c42a0c81e29ea087de5ddd3a5f00
Reviewed-by: hjk <hjk121@nokiamail.com>
Broke with f1eb9c4827 which exchanged
setDefaultKeySequence with setKeySequence
Task-number: QTCREATORBUG-10538
Change-Id: Id40bd8fd403cd586a39a19c248f59e23cf4cf8c0
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
Reviewed-by: David Schulz <david.schulz@digia.com>
This makes the specializations responsible to register the environment aspect
that makes the most sense for them.
The only real user of this is the QmlProject, which added its own
EnvironmentAspect on top of LocalEnvironmentAspect set by the base
class.
Change-Id: I2ad8c23a008e249dc919491a5fd397ec04502375
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
Open the "Run" view by default when switching targets in projects
without build settings. The build settings view is not what the user
wants in that case.
Change-Id: I14b5d32fa3fdfef1ba7d4f9f6af383d28021baa8
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
Describe the new platform codegen and linker flags options
and the custom parser settings.
Update and add screenshots.
Change-Id: I64498258930ce1f912bcd8891a6b55f40d903f2c
Reviewed-by: Fawzi Mohamed <fawzi.mohamed@digia.com>
Reviewed-by: André Hartmann <aha_1980@gmx.de>
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@digia.com>
Add link to "Viewing Function Tooltips".
Update screenshot, because the tooltip fields were moved around.
Change-Id: Ic5e8d3d8c9a859c6a6748d631640b42239ea6f3f
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
Using disabled did not give any visible feedback.
Change-Id: I67bb9cd83c7d36c5899e40a91e9a6a34cb882ec4
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
We constantly get feedback that clearly shows that
users do not understand how sessions work.
Updated screenshots.
Change-Id: Ifcf3b08ca2f27e14085a5d84adaeacddc59588d8
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
