"Calls of functions that start with an uppercase letter
should use 'new'." is a warning, not an error.
Fixes: QTCREATORBUG-27522
Change-Id: If1f82665819053b72e412a51cf4cf3c9b3e91ae2
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
... by not overwriting DumperBase.qtVersion. This function already
checks whether the Qt version was passed via the fetch variables
command.
amends 3aee50f5fd
Fixes: QTCREATORBUG-31049
Change-Id: Ifa67be5701fc7e5492e4c1fcb8943111b299c78d
Reviewed-by: hjk <hjk@qt.io>
This fixes the issue at least for all usual FakeVim commands.
It still breaks if the user directly uses the respective
buttons on the editor toolbar, but that is a different story.
Amends 5ad790d5c8.
Task-number: QTCREATORBUG-28914
Change-Id: I0a69d1f50eb6788099ac93bb529f72502cbd6ed0
Reviewed-by: hjk <hjk@qt.io>
This is a temporary fix until the real fix ends up in Qt 6.9
and we start using QDoc from there to build the docs. Then,
we can rethink the title.
Change-Id: I95332b18f7b53fd9b01d0b986275c958add0f00e
Reviewed-by: hjk <hjk@qt.io>
When starting the debugger, we need to pass it the location of the
downloaded device symbols, or otherwise debugger startup is very slow.
Xcode changes the location where it saves this information once in a
while, and it must have again. The location with Xcode 15.2 at least is
in the style "iPhone8,1 15.7.3 (19H307)", i.e. it starts with the
"product type" now.
Retrieve the product type of the device and add another candidate
directory for device symbols.
Fixes: QTCREATORBUG-31044
Change-Id: I1a65305fc84c1af8cd48c4ebb249167e1dbe6ae1
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
This updates the existing mode bar icons in the svg file with the new Qt
Creator Design icons from Figma. The pngs are updated accordingly.
For consistency, the "beetle overlay" for toolbar actions is also
updated.
The custom color for "active" state of a mode icon has been removed. If
we keep this change, a couple of Theme::IconsMode*ActiveColor entries
can be removed.
Change-Id: I9b5422c79f5426e31b41e59d67ddc307b521c0af
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Reviewed-by: hjk <hjk@qt.io>
When closing the "Preferences..." dialog with Esc key, the ASAN address
checker would report a use after free at "while (m_running)" below in
the code.
Fixes: QTCREATORBUG-31047
Change-Id: I484a80305ebbd903607e945eb56b331f57d40370
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Organize quick fixes in tables in alphabetic order
according to where they are available.
The one big table was getting very hard to read and
new quick fixes are added all the time.
Change-Id: Ieaff98b7cdb2d781b14630fa4db77b4b261f4573
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
After the recent change 3be0b263a8,
SettingsHandler::getPath() can be called one additional time in the
McuPackage constructor. Take this into account in test expectations
Change-Id: Ib302de2b2d446a9b8884f8c3d0bfabd4223b8d87
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
The plugin class names were different, and this is important for static
plugins because the symbols wouldn't be found at linking time.
Change-Id: Ia2254e5ce811fe23daf12e445593980211b7cd47
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
For plugins that are shipped by Qt Creator, it makes sense to disable
experimental plugins by default. But for separately installed plugins it
is weird that you first have to download and install them, and then also
have to explicitly turn them on.
Use that for AppStatisticsMonitor in the case that it is built and
installed as a separate plugin.
Change-Id: I12e979d2e088dc32380c2e2ae83ed2b7ef9276b0
Reviewed-by: Artem Sokolovskii <artem.sokolovskii@qt.io>
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
qdoc needs a new environment variable these days.
Change-Id: I29eb64c2d3ee7555fc99a928971eaccaac8317bf
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
fromJsonValue<T>(...) (with T = MarkedString) always tried to convert
the json value toObject() first. Which is wrong since it can be an
object or a string.
Fixes the broken hover text for the json language server.
Change-Id: Id69b4270238bea7068936a7d2142f4f94918f96b
Reviewed-by: David Schulz <david.schulz@qt.io>
The win32interrupt.exe is gone. And since we do not support 32bit Qt
Creator builds anymore there is no purpose for a win64interrupt.exe.
Since some 'recent' changes interrupting the cdb works now by simply
setting Process::setUseCtrlCStub and calling Process::interrupt on the
debugger process. The same seems to work with gdb nowadays, but we need
to expect the SIGINT signal that gdb receives in this situation.
Otherwise the user will be shown a message box about the emission of
that signal.
Change-Id: I7a21d7ea34409d8bbf62d94e28387d591e7feb3d
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
The text editor widget now tells us when it thinks a new navigation
point should be added, so do it.
Change-Id: I20e65134420cb1d94d7bc5310791d07ff951647c
Reviewed-by: David Schulz <david.schulz@qt.io>
It looks like there are Qt-using scenarios without easy way to have
the right Qt version in the kit,
Among the frequent cases where we need to distinguish Qt versions in
the dumpers are the Qt5/6 container layout differences which can in
some cases be detected from the currently dumped value. Use that now
as the primary distinction and fall back to the previous expensive
peeking only if that is needed. This also postpones any Qt version
related activity until a real Qt type is encountered, i.e. does not
impact non-Qt scenarios.
Task-number: QTCREATORBUG-31033
Change-Id: I67b6e34c42994ad9f6e8ec8698b430b55327cf0c
Reviewed-by: hjk <hjk@qt.io>
Reviewed-by: David Schulz <david.schulz@qt.io>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
