Save them also whenever a settings save is requested, which e.g. also
happens when closing the options dialog.
Change-Id: Ic20f1007381a4d0a8157f17fd24c0d8ea24907ee
Task-number: QTCREATORBUG-16576
Reviewed-by: David Schulz <david.schulz@qt.io>
The QML compiler can run asynchronously and produce ranges that don't
match up with other QML/JS ranges. The statistics model assumes that
all ranges are perfectly nested, and produces incorrect data if they
aren't. The compile ranges are perfectly nested among themselves, and
the other QML/JS ranges are also perfectly nested among themselves, so
we can fix this by keeping separate statistics for them.
Also, choose a less insane data structure for the relatives model.
Change-Id: I146593b67586e7b5aba6b19d360961c142511289
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
Clicking on something in the QML profiler should never trigger a switch
to a different mode.
Change-Id: I4784e836b0091d44fd046b605c49d2b10b3e8c34
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Reviewed-by: Pasi Petäjäjärvi <pasi.petajajarvi@theqtcompany.com>
Preparation for easier distinguishing arguments for performing
normal run versus debug run.
Change-Id: I41cfa7fca5730f721b5b6a980c82c015f9e7f914
Reviewed-by: David Schulz <david.schulz@qt.io>
The "TranslationUnit parts" moved already to TranslationUnitCore.
Change-Id: I2bea7847e2b3e84fbfacc3d2dc43f180873349ac
Reviewed-by: David Schulz <david.schulz@qt.io>
The QmlDebugConnection might immediately signal a connection failure
on connectToHost() or startLocalServer(). If the timer is not running
then, we trigger the QTC_ASSERT in qmlDebugConnectionFailed(), which is
meant to make sure that we don't silently give up. In this case, we
haven't even given up, yet, as the timer is in fact started afterwards.
Change-Id: Ia2c107d9b511092eaf32380203a3b4628139d320
Reviewed-by: hjk <hjk@qt.io>
The template id for the class name is missing, but it's better than
nothing.
For example:
template<class T>
class Foo
{
void func() {} // Move Definition Outside Class
};
// The following lines are added
template<class T>
void Foo::func() {} // Should be Foo<T>::func
Task-number: QTCREATORBUG-16649
Change-Id: Icb560e0b87f563cbda18f4742f44bb8ef4d8a900
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
The template id for the class name is missing, but it's better than
nothing.
For example:
template<class T>
class Foo
{
void func(); // Add Definition
};
// The following lines are added
template<class T>
void Foo::func() // Should be Foo<T>::func
{
}
Change-Id: I60a0cbd348985def3dfb7037067786e942278593
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
Do not require directly passing the enclosing template.
Change-Id: Ie03bc58338fe003677a5f5311d86d70f499373ee
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
This was done for the "kill by process name" operation, but not for the
"kill by PID" one.
Change-Id: Ia8eb57d1fa030624470489dbd0e7b03093fd822b
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
Using Qt5.6 and Xcode 5 or Xcode 6 results in compile
issues.
Change-Id: I33af400f51991e043672712b531869c6a79d6ffd
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Which outputs the information from qtdiag, installed plugins,
and general Qt Creator build information.
Task-number: QTCREATORBUG-16135
Change-Id: I618b9883369bae45006bb109f8757e89b091b882
Reviewed-by: David Schulz <david.schulz@qt.io>
At least display results for using gdb or lldb and inform
user that we are not able to do so when using cdb.
Task-number: QTCREATORBUG-16693
Change-Id: I1a98a79aaf76de47b5dcb58d4dca9247f1642d36
Reviewed-by: David Schulz <david.schulz@qt.io>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
The function qmlJSAutoComplete() will be used by the QmlDesigner.
Change-Id: If569e3f22e2dd934b9043b2e139da597686496ae
Reviewed-by: Marco Benelli <marco.benelli@qt.io>
We don't want to disable RTTI in unittest so we require to compile them
with RTTI. You can disable yourself RTTI if you don't want them for some
reasons.
Change-Id: I76d05a36442305f379ce3d88b3f6ed4372127002
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
The linker does not understand the -fobjc-link-runtime option. Use the
cpp.driverFlags property as a workaround. Technically, it should use a
property that is only applicable when the toolchain driver acts as the
linker, but we don't have it (yet).
Change-Id: I0707e08726f54a329feb440f2d8a984c12de9f4f
Reviewed-by: Jake Petroules <jake.petroules@qt.io>
Which seems to have issue to construct a std::function<void(T)> from a
function pointer to a function that does not return void.
Change-Id: I10d79f328acb922dac298ec598eecff1d3b9f522
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
As this slot is triggered by a queued connection the document
can change between emitting the signal and the assert.
Task-number: QTCREATORBUG-16221
Change-Id: I29cb6cd8546e38863318393e2cc39fa791cf20d6
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
This resulted in wrong cxx flags for the clangbackend, which couldn't
compile algorithm include file for example then.
Change-Id: Ida7bebf2435e1bc031b62204d169cf008a189f25
Reviewed-by: Marco Bubke <marco.bubke@qt.io>
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
If for some reason the todo settings are borked, do not crash/assert.
Also, avoid overwriting existing settings with default settings, if
for some reason the todo plugin is never initialized (because a
dependency fails to load).
Change-Id: Id7815b799adaff3dcdf00fedb9ade3ced01e23b9
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
For macOS with keys Home and End, for the others with
Ctrl+Home and Ctrl+End.
Change-Id: I73cde89b57bc3cce89c6638d2692bcafbd4710af
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Even though the tab was selected. Broke with
e440e344ca and
abcdadd40e .
We need to update the current index when tabs/modes are inserted before
it.
Change-Id: I26b5252d365c0108584534bcb0ee1aacc3eacce3
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
I also added the qtc prefix to all logging categories.
Task-number: QTCREATORBUG-16767
Change-Id: I04214dba9912fe6c669f10566582d6009b5d75f0
Reviewed-by: Robert Loehning <robert.loehning@qt.io>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
