Paths passed to Qt Creator API must be cleaned. Make sure that the file
path that is opened from stack view and when stepping etc, is cleaned.
Task-number: QTCREATORBUG-10119
Change-Id: Iaac9b15e76cf8dff514889f201c4f65330145d16
Reviewed-by: hjk <hjk121@nokiamail.com>
Instead of actual file.
In case currentFile is a directory, it is cleared, and project top level
is used instead. This leads to unexpected results.
This patch corrects repository resolution in stash dialog when opened
inside a submodule.
Task-number: QTCREATORBUG-10397
Change-Id: I070cc7f9cbebe3be800dbbb9569cf73f540a6d14
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
Change the preprocessor popup to a dialog.
Save the additional preprocessor directives to the session instead of the
.pro.user file.
Change-Id: I0d08c5684cfb21e822cde0a965c9cf14e5d6d47d
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
This is the first phase of fixing bug QTCREATORBUG-10320.
This change resolves typedefs of template parameters(and resolves
problem with endless loop).
The next step will be matching appropriate template specialization
(this is needed to solve problem with missing code completion).
Missing matching: template specialization with the same parameters,
e.g.:
template <class T1, class T2, class T3>
class T
{
};
template <class T1, class T2>
class T<T1, T2, T2>
{
};
Task-number: QTCREATORBUG-10320
Change-Id: Icb6b539c021b2a67a66db9011a2e627f7d96526b
Reviewed-by: Przemyslaw Gorszkowski <pgorszkowski@gmail.com>
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
Do not trust kits with an invalid id, as there is no way those
could have ended up being saved out by creator. Safe all other kits
that were constructed using Kit(const QVariantMap &).
This new constructor uses the code that used to be in fromMap(...),
with some simplifications.
Remove fromMap(...) method from kit as it is no longer used.
Change-Id: Iac28ea9b85670e03088a4b7c5283af6b4b70c0fc
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
We cannot technically enforce a remote process to actually terminate,
but we don't want the associated DeviceProcess to "hang" forever.
Therefore, we now
a) check whether the kill operation reports an error and
b) start a timer after starting the kill operation.
If the kill operation either "officially" fails or does not have the
desired effect of actually terminating the process within a given time
frame, we set the DeviceProcess to "finished" manually. This is the same
thing that already happens when the connection gets lost, where we also
report the DeviceProcess as finished, even though the remote process
might still be running.
Change-Id: I5620f90453463c64d3a84abd30f1ec7eec9d492d
Reviewed-by: David Schulz <david.schulz@digia.com>
creatortypes.py wasn't included, and some d. qualification missing.
Change-Id: I1f444358cc1489f47083af39565147576f1885b7
Reviewed-by: hjk <hjk121@nokiamail.com>
This avoids useless validation runs during construction.
Also reorder member variables to save a couple of bytes
in the structure.
Change-Id: Ibc33b89f12c306852af02d387ee2d177f732bb83
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
This fixes the rendering of the AbiWidget if no ABIs are deteceted.
Change-Id: I9ef4aec70e88add498fd60f29014d6bf91e0ee61
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
Stay below the radar during construction/fromMap. This avoids some
signals from the KitManager about unmanaged kits having been updated.
This signal is used in three places only and always connected only
after the the construction happend. So this should be safe.
Change-Id: If6cc29b6bb98fa161776a9a79f48f88173db04b8
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
Reviewed-by: hjk <hjk121@nokiamail.com>
The SessionManager is disconnected at that point already, so we were
never told that projects were destructed already and were happily
calling into those.
This fixes the crash described in QTCREATORBUG-10354.
Task-number: QTCREATORBUG-10354
Change-Id: Ib8ce07d6db38dbff9154b127f5fb620a9961c742
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
This reverts commit c5dfcce948, but the
bug addressed by that commit remains fixed. FunctionHintProposals need
to be fragile so they can be replaced by e.g. GenericProposals. Only one
proposal can be "active".
Change-Id: Ibca40063d46b8ef3bce4d72be7488f70885e75da
Reviewed-by: David Schulz <david.schulz@digia.com>
Also bump the minimum Qt version required for new Qt Quick apps to 4.8
Change-Id: Ieeabc8475ccfa7f9fec7ca08cd88384ed88f0d1d
Reviewed-by: Christian Kandeler <christian.kandeler@digia.com>
Change-Id: I10e5f7b4c9d0d527f8df34aa425a2a0bdaac5243
Reviewed-by: David Kaspar <dkaspar@blackberry.com>
Reviewed-by: Nicolas Arnaud-Cormos <nicolas@kdab.com>
