If the target is the parent we want to anchor to the same edge by default.
If the target is a sibling we want to anchor to the opposite edge by default.
If the anchor target is changed we have to evaluate this.
Change-Id: I80ee52da7537435956880bcc132c2bc34ddfc0ed
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
Came from two deletions at the same time QCache::remove and
delete on sharedMemory.QmlDesigner:
Change-Id: I6a29cf160c8e81ecd955cf36999edc639fbbb63f
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
If we don't find it in the java folder we return the templates folder.
Change-Id: I8a9c478ed3f9e32e9ed8c656545ab90c18204e52
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
To be sure that the shared memories are removed at process exit.
And fix that createSharedMemory reuse possible already existing shared
memories now. ("take" -> "[]")
Change-Id: Idcc99ba42b862b862d5403ecf3b781a27fdf757f
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
Before the working directory was the working directory of Qt Creator.
If the working direcotry was the bin diredtory of Qt Creator the puppet
picked up the qt.conf from Qt Creator and could not load the platform
plugin.
Change-Id: Iab22267c578fc837b1b52bded850f0033618811c
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
We have have to check and handle sourceComponent and component (Tab).
Change-Id: I736648fc09fe4ee3333c4524666e3acea500804a
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
Loader was also interpreted as a component, but the handling
of component and sourceComponent was incorrect.
Change-Id: I5cd691ece1a29c77b52dc74785013f08d589b2eb
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
OS X is only supporting a maximum of 31 letters for shared memory names.
Change-Id: I61351228decaa3fa7ec19a6035620ab932cf5386
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
The crash happens on Linux/Xming. 2 subsequents calls to
slotRefreshCommitData occur, m_commitDataFetcher is released when the
first one is handled, and the second call dereferences NULL.
Change-Id: Ibc06fe5dd89b790ac84544f6842cbf345d118703
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
Winrtrunner was called with the executable file path for the
top-level .pro file, which happens to be the empty string.
We now store (and use) the right .pro file path.
Change-Id: I7d71e6b99393e863f3ba0df2d2902f29d75a9583
Reviewed-by: Christian Kandeler <christian.kandeler@digia.com>
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
Nested event loops are dangerous and in this case lead to a crash.
So change the api of ensureConfigured to not use a nested event loop.
The CustomExecutableRunConfiguration then has to manage the dialog more
explicitly. Also this makes the dialog non modal, since it should then
cope with every situation.
Task-number: QTCREATORBUG-11416
Change-Id: I2af782915c148f8dff1b0df54fdb64aa83f684d2
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
The menu is expected to be populated after the signal is emitted.
Change-Id: Ibcb9eaf3742942801ad79b98000d48cb93d5ae31
Reviewed-by: Jarek Kobus <jaroslaw.kobus@digia.com>
We use left padding instead of a prefix.
Task-number: QTCREATORBUG-12781
Change-Id: I0c89e3592ad0ca9c498d33930ef2742ec970f8bb
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
This is a workaround for user mistakes and should not be generally done.
It can result in e.g. redundant relinking.
Change-Id: Ia14854c9d260f5d7a8175d105b9bce896fcdeebf
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
The qbsProjectData() member function always returned the top-level
project data, which messed up a couple of things, for instance
"build sub-projects" and the node tree updates.
Instead, return the project data corresponding to the node.
Change-Id: If40c441c62334f0069a5fe3cb4873cf973baf135
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
Flipable, StatusBar, and ToolBar are no longer visible
in the Library pane.
Change-Id: I5258ff950e83a49c90b5246d5957d8c9e6382657
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
Just doing as the great wise frog tells me.
Change-Id: I73c07142cd902ac3b89f8c00597087d7d550a2ee
Reviewed-by: Christian Stenger <christian.stenger@digia.com>
Some imports are known to create trouble in the designer.
There is no reason to allow adding imports using the designer, that
will just create issues.
Change-Id: I95437f39c02fd06650285a5184a77669ae32b705
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
This was introduced by adding the remote linux support for 3.0 in
328a24edee. If the user cancels the
run cmake dialog, no buildconfiguration is created. The adding of kit
should then not happen. A target without a buildconfiguration should
not happen.
Task-number: QTCREATORBUG-12773
Change-Id: Ic43c5cc13f9e114ea24cc97154a6c084125f6318
Reviewed-by: Christian Stenger <christian.stenger@digia.com>
Should be impossible to do, but the stacktrace in the linked task shows
that it is possible somehow.
Task-number: QTCREATORBUG-12776
Change-Id: I1f2054bbaa132c29dfc4579fb7020f364bddd939
Reviewed-by: BogDan Vatra <bogdan@kde.org>
