We are happy to announce the release of Qt Creator 4.15 Beta!
General
We added a locator filter for opening files from anywhere on your disk. This locator filter was already available on macOS using Spotlight. Now it also is available on Linux and Windows, and can be configured to use any external command line tool that returns a list of files. The default setting is using "locate" on Linux and "everything" on Windows.
Sometimes it is difficult to configure the environment variables that are set when Qt Creator is run, which in turn affects external tools run from Qt Creator. We added a global option for this in Tools > Options > Environment > System > Environment. This adapts the system environment which is then further modified by the kit environment, the build environment, and the run environment.
Editing
Please see our change log for the long list of fixes that were done for the C++ support. I'll just mention here that you now can filter the result of searching symbol usages by access type.
The QML editor can handle inline components now, and received some more fixes for advanced JavaScript features.
We simplified the configuration of a Java language server, and generally improved support for it.
Projects
We fixed several issues that made it hard to configure CMake projects that have special prerequisites to successfully parse at all. Aside from multiple other fixes, Qt 6-based CMake projects can now also target iOS.
We added basic support for "ctest" as well.
There is a new option for running applications as root from Qt Creator.
Please check our change log for a more complete list of improvements.
Get Qt Creator 4.15 Beta
The opensource version is available on the Qt download page under "Pre-releases", and you find commercially licensed packages on the Qt Account Portal. Qt Creator 4.15 Beta is also available under Preview > Qt Creator 4.15.0-beta1 in the online installer. Please post issues in our bug tracker. You can also find us on IRC on #qt-creator on chat.freenode.net, 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.
Thank you for making macOS usable again! (QTCREATORBUG-22123 )
Importing and parsing CMake projects is still fragile and error-prone (https://bugreports.qt.io/browse/QTCREATORBUG-24637). There are still 3 related commands under Build drop down: "Run CMake, Clear CMake Coniguration, Rescan project". If I make a mistake in the initial variables section, I need to
It would be nice to make this more robust. If initial project resolving fails and I change one of the variables, QtCreator should try to re-resolve the project in a 100% clean environment. And I would like to see a resolve button in that dialog that does exactly this.
Just a note that you can set/change variables in the configuration table after initial configuration - even if initial configuration failed. But I agree that this is not great or intuitive or anything. It is very unclear what the "Initial parameters" actually represent / when they are actually used. Some button "Clear CMake configuration and configure with initial parameters" or such would probably already help a bit.
Thanks, but as already written in the bug report: if project resolving fails again, all values are removed from the configuration table (still happens in 4.15 beta).
IMO the parameters in the "initial CMake parameters" field should be read-only or should be synced back and forth with the the kit configuration. If I change those variables in the kit later on, the project falls out of sync. That's annoying.
Take Qbs project resolving in Qt Creator as an example. It's way more robust, less error-prone and easier to use.
QtCreator still can't show output (qDebug(), Log.i(), etc.) from Qt Android Service processes. It would be handy to have this in 'Application Output' (maybe dedicated output window for each process of application). https://bugreports.qt.io/browse/QTCREATORBUG-24496, https://bugreports.qt.io/browse/QTCREATORBUG-16887