The commands provided with the capabilities are not the only allowed
commands, but the ones that can always be executed.
Change-Id: Ie005fafe2e64c334f67809c00623dec2901972c6
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
... when trying to complete the name of a function definition. libclang
tags such completions as "not accessible", even though we are not in a
call context.
Fixes: QTCREATORBUG-25244
Change-Id: I4b03b1a43be7a85c37c7d2b2bfe2d83112075674
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
In some cases the last floatingWidget seems to be
partially destructed. Checking for the parent checks for
this case.
Change-Id: I27cb750d846e71b9ab4423700120e2c659a02adc
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
* Paint red label on the arrow with event id if only one event is
connected
* Cleanup label painting for multiple events
* General code cleanup
Task-number: QDS-3481
Change-Id: I9652c1767ccaeb07b03c35e0fd4fec41d496c210
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
This seems safe, as the arguments to the async function that the future
results from are values and shared pointers, so there does not appear to
be a need for this object to stay around while it finishes.
(cherry-picked from commit fd22787a69)
Fixes: QTCREATORBUG-25121
Change-Id: Ib498551856942bf7c3d05c3013e12ad6d90fd762
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
This is now available for Text and TextInput types
(and annotations).
Fixes: QDS-3570
Change-Id: If0d3a19d7d99fac08abf7d9513058d147859eb07
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
In case of no line number, but file name.
Change-Id: I2c51e5834e113c8f98b018df361b0504c4bd79f9
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Apparently this one never worked, but as we don't use it in our own
code, that went unnoticed.
Fixes: QTCREATORBUG-25236
Change-Id: Ia013baf3ca2fd01cc14b72d9c6a5f73426539d00
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
- Updated the screenshot in the "Using External Tools" topic to
show currently available variables and the Variables button.
- Added a link to where the variables are described in more detail.
Fixes: QTCREATORBUG-25233
Change-Id: I1a023d478f239a2fa5a648b36fe22e99435c65b3
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
On Windows applications may print to the Windows internal
debug console. This output is retrieved and passed around as
DebugFormat as it is impossible to guess whether stdout or
stderr had been used when printing.
But output in DebugFormat had been ignored so far - fix this
and handle this as inside the Qt test parser.
Fixes: QTCREATORBUG-24560
Change-Id: Ic5e3723c3e3e47556264e4c5cf719706ee7eaf1c
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
for std::map, std::set and std::list
Fixes: QTCREATORBUG-24901
Change-Id: Ibfb196b17b7270729b052ed27dd51786cb2f8db8
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
By looking for debug members instead of relying on a failing size check.
Task-number: QTCREATORBUG-24901
Change-Id: Ia79ba893243e864c7808e89ee7e29ba4b853f754
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
If a subdir in a subdir .pro file is excluded from the build with a
scope, it still is parsed with an exact parser
(in case cumulative parsing fails? see e.g.
440c40f534)
In that case we may not add issues to the issues pane from the exact
parser though, since for the subdir it is unexpected to be handled in
that situation. Post to messages pane like before (without popping it up
though).
Fixes: QTCREATORBUG-25201
Change-Id: If626a5cbc0001170f28bce89ae17394323af2a7b
Reviewed-by: hjk <hjk@qt.io>
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
When for example closing all editors, the selection in the project tree
is removed, but after re-opening the previously selected file, the
selection was still missing.
Qt item views differentiate between "current" item and "selection". The
code uses the "current" item for tracking, but when clearing the
selection in the project tree, the code did not "clear" the "current"
item.
Change-Id: I182c7b78bf8dcc51af71e860ac620310d472b7b5
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
This avoids the warning
QIODevice::write (QProcess): ReadOnly device
in cases where the process is run inside a read only
directory even when the process has no input.
Change-Id: I9434c738e9cf94c348f1437ebf15e1c7574cde94
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Reviewed-by: hjk <hjk@qt.io>
CLANG_INCLUDE_DIR and CLANG_BINDIR are the fallback paths that are used
if no bundled LLVM/Clang is found, so these must be absolute paths to
the build-time LLVM/Clang installation.
This also removes the need of copying LLVM/Clang into Qt Creator's
build directory.
Fixes: QTCREATORBUG-25147
Change-Id: I052138d894c316f493423b1da0ba79af633c4c37
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
The editor manager emits currentEditorChanged() before editorsClosed(),
which throws off the clangbackend. Fix this by sending an extra
DocumentVisibilityChangedMessage after the DocumentsClosedMessage.
Fixes: QTCREATORBUG-25193
Change-Id: Ic02ae174a2912d79aeded44ced13d962b53526b1
Reviewed-by: David Schulz <david.schulz@qt.io>
No QRegExp in Qt 6 anymore, use QRegularExpression.
Amends bebd70573e
Task-number: QTCREATORBUG-24098
Change-Id: I1f65a400d27d710b6393fb3568e8fc020ccb194e
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
We called QTreeView::visualRect() with a potentially invalid model
index, yielding a bogus QRect, from which we derived a bogus QPos, at
which we tried to show a tooltip, which crashed Qt.
While the whole logic around that code looks dubious, for now we just fix
the crash by using a persistent model index.
Fixes: QTCREATORBUG-25170
Change-Id: I5647d0ed04bd228bb2887ef06465212545b54f57
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Allows e.g. distributions to adapt to system layout.
Fixes: QTCREATORBUG-25142
Change-Id: Ia6d759514fef5a154334bc3d7221ea4b970122f2
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
The code model may provide selections that are not ordered
as they appear inside the document due to the declarative
nature of QML.
Ordering before using them avoids couple of warnings stating
"overlay selections not in order".
Change-Id: Ie912e94aa01ffde52b01dca7a9bde24ae02e8b33
Reviewed-by: Fawzi Mohamed <fawzi.mohamed@qt.io>
By first checking for it in the system, then if the internal copy
is checked out.
Fixes: QTCREATORBUG-25144
Change-Id: I839591cc8e311948a21685384de574e7330a6ee5
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
To see the results use
QT_LOGGING_RULES=qtc.qmljs.imports.benchmark.*=true
Change-Id: I07fe7b71d893423f3dfe5f9c0f1410bd29312943
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
