We are happy to announce the release of Qt Creator 13!
General
- We provide offline and online installers for Linux on ARM now!
- We updated the visual style for Welcome mode. Also see the separate blog post on Qt Creator themes.
- We improved the docking UI that is currently used in Debug mode and Widget Designer. The "locked" state is gone, and instead you can always drag panels around at the titles. For multiple panels that are layed out in a vertical stack, we added the option to temporarily collapse individual panels.
Platforms
- We added support for creating, building, deploying, running, and debugging applications for devices that use the Qt Application Manager (for Qt 6 and CMake based applications). (Documentation)
- We added partial support for iOS 17 devices: Detection works, and you can deploy applications and run them. Debugging and profiling is unfortunately not supported at the moment, and we also cannot access the application output. These are current limitations of the new tool that Apple provides for access to devices with iOS 17 and later.
Projects
- We changed the default build directory to be within a "build" subdirectory of the project sources. This was needed for Docker support, but also is a very common pattern for CMake projects. Of course, you can still switch back to a different default build directory in Preferences > Build & Run > Default Build Properties > Default build directory.
- Vanished targets: If you open a project that was configured for a kit that is no longer available, Qt Creator created "Replacement for ..." kits automatically. Qt Creator 13 instead lists these targets in a "Vanished Targets" section in Projects mode, and allows you to create a kit, or copy the preserved build, deploy, and run settings to a different kit there. (Documentation)
- You can create Python kits for your Python projects with the "Generate Kit" button in the Python interpreters preferences now. (Documentation)
Editing
- Qt Creator can now set up language servers for YAML, JSON, and Bash for you (via npm). (Documentation)
- You can now navigate from QML components to the corresponding C++ code in the project.
- The Clang Format settings were re-organized. Custom settings are now a text editor with syntax checking. (Documentation)
- We fixed that "Follow Symbol Under Cursor" only worked for exact matches with Clangd. It now uses the built-in code model as a fallback if no exact match is found.
There have been many more improvements and fixes in Qt Creator 13. Please have a look at our change log for more extensive details.
Get Qt Creator 13
The opensource version is available on the Qt download page under "Qt Creator", and you find commercially licensed packages on the Qt Account Portal. Qt Creator 13 is also available as an update in the Qt Online Installer. Please post issues in our bug tracker. You can also find us on IRC on #qt-creator on irc.libera.chat, and on the Qt Creator mailing list.
You can read the Qt Creator Manual in Qt Creator in the Help mode or access it online in the Qt documentation portal.
Commenting for this post has ended.
Great, thanks! This looks awesome: "You can now navigate from QML components to the corresponding C++ code in the project." However, it does not seem to work. In QML, I have this line:
required property CMyCppClass pData
It's registered in a QML module (via cmake's qtaddqml_module), the module is imported in the QML file, but follow symbol under cursor on the type does nothing. Did I misunderstand something?
Please have a look at the original report/suggestion at https://bugreports.qt.io/browse/QTCREATORBUG-28086
I do not exactly know the limitations of this, it might only work for components that you instantiate in QML with MyComponent {} (like in the code snippet there)
"You can now navigate from QML components to the corresponding C++ code in the project." do I have to do something to make it works? At first sight, it doesn't works for me
Nice release! The video is broken for me.
Do you mean the https://www.qt.io/hs-fs/hubfs/dock_debug.webp?width=890&height=610&name=dock_debug.webp ?
WebP file format is supported on all major browsers, see https://caniuse.com/webp
Interesting, looks like this is about the size parameter:
This works: https://www.qt.io/hs-fs/hubfs/dock_debug.webp
This looks like modern art: https://www.qt.io/hs-fs/hubfs/dock_debug.webp?width=445&height=305&name=dock_debug.webp
Another thing: The blog post is set to 22.03.2024 and thus shown way down below in the blog page.
More things broken with the CMS :/ Date updated manually now.
There is your answer (:
The CMS seems to have issues with delivering scaled versions of the webp (with odd width?). I've updated that to even width, does that fix it for you? (Clicking on it to see the original should always work)
Yes, the video inside the blog post works now, but it's a bit small. Just remove the hard-coded width: 484px; and it will display it 100%.
In the new release the "welcome" screen became barely legible for me with the default theme. The font is too small (and bold green on a gray background to boot).
Qt Creator 13, error path with visual studio 2022 and qmake build system. empty console project
Qt Creator 12 is work.This fixed with 13 version in file .pro
I have created a Bug report for an issue we found that is at least similar: https://bugreports.qt.io/browse/QTCREATORBUG-30659 If you can, please add your own system setup as a comment to the ticket, specifically your source and build directory.