GitLab

These causing warnings when applying translation patches.

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

For some reason gradient stops end up in the navigator model.
This should be fixed for 3.1.

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

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

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

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

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

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

At least theoretically, on our side. Practically the output
seems to arrive all with ldb.SBProcess.eBroadcastBitSTDOUT
from LLDB.

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

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

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

disconnectClientSignals only disconnects signals of objects that are
deleted directly afterwards. As deleting a QObject automatically
disconnects its signals it's unnecessary to explicitly do that before.

However, if QmlProfilerClientManager is deleted from the destructor of
QmlProfilerTool, receivers of those signals may have already been
deleted. This can lead to crashes.

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

Following matches are likely to be merges, and not the branch that the
first commit originated from.

Change-Id: I80a442bf9f7bc7f5859a1f4c3d3e167d55b28241
Reviewed-by: Petar Perisin <petar.perisin@gmail.com>

The remaining patches are currently not actively used, and unlikely
to be used again in the future.

Change-Id: Ie2cc47d5076f5e28b8182c0ff06621f576c81d34
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
Reviewed-by: David Schulz <david.schulz@digia.com>
Reviewed-by: Rainer Keller <rainer.keller@digia.com>

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>

Helps debugging ...

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

Change-Id: I004a07c1b047c1ff6a390e5432f97a299781568d
Reviewed-by: Nicolas Arnaud-Cormos <nicolas@kdab.com>

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

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

Change-Id: I01374545ec3882a1dc9b08adccf4632f38438efb
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
Reviewed-by: Fawzi Mohamed <fawzi.mohamed@digia.com>

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

Change-Id: Ic55389ee8200e3f78f8bb0752411b0a0ae5d5e62
Reviewed-by: Fawzi Mohamed <fawzi.mohamed@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>

Change-Id: Ia52237760d36f342d6b053525ca6617a1e722aab
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@digia.com>

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

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

Task-number: QTCREATORBUG-10599
Change-Id: I091db84c81b0ad031744142568cc37d648e9dfb7
Reviewed-by: Andy Shaw <andy.shaw@digia.com>
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>

Update screenshot and add a new one.

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

Change-Id: Idd0e0a4486d6d94194d3a144fc238b93128ecf6b
Reviewed-by: Daniel Teske <daniel.teske@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>

Remove infrastructure to debug/inspect QML applications with Qt 4.7.

Change-Id: I277e9884e009475a29017f502bbe1d069317460f
Reviewed-by: hjk <hjk121@nokiamail.com>
Reviewed-by: Eike Ziller <eike.ziller@digia.com>

Broke with f1eb9c48

 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>

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

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