Eike Ziller

Qt Creator 4.0 RC1 released

Published Wednesday April 20th, 2016
24 Comments on Qt Creator 4.0 RC1 released
Posted in Dev Loop, Qt, QtCreator, Releases

We are happy to announce the release of Qt Creator 4.0 RC1 !

I’d like to refer you to the beta blog post for an overview of the new features coming in the 4.0 release. Since then we have been fixing bugs busily, and we believe that what we have now is very near to what we can release as the final 4.0 release soon.

Our icons and the new “Flat” theme also received a lot of polish, and “Flat” is now the default theme for everyone who hasn’t ever changed the theme in Qt Creator. The old theme is also still available as “Classic” in Tools > Options > Environment > Interface.

So this is a good time to head over to our download page or the Qt Account Portal, get and install the RC and post us your feedback, preferably through our bug tracker. You also find us on IRC on #qt-creator on chat.freenode.net, and on the Qt Creator mailing list.

Do you like this? Share it
Share on LinkedInGoogle+Share on FacebookTweet about this on Twitter

Posted in Dev Loop, Qt, QtCreator, Releases

24 comments

Babilon says:

I thank you very much for leaving classic theme as an option.
#hateflat

Lilian says:

People like being vocal about negative things.

I find it pretty nice, and the icons are clean and beautiful.

#LoveFlat!

sap says:

ill be vocal about positive things too then: i love qt creator and i love the new flat theme!

good job qt developers you guys rock!

Sebastian says:

Will there be any performance improvements? This version is unusably slow for me (as was the beta before).
I suspect the Clang code model (previously used the builtin which seems to be gone now).
Win7 MSVC2013 corei7 no SSD

Eike Ziller Eike Ziller says:

To use the built-in code model, turn off the experimental ClangCodeModel plugin in Help > About Plugins (and restart)

Arthur Turrini says:

Yes, ClangCodeModel is very nice but it is pretty slow sometimes.

When detecting pointers for autocompletion it is very slow.

QFile *f = ….
f. (take a deep breath) and the -> appears.

Robert Löhning says:

This issue is being tracked in https://bugreports.qt.io/browse/QTCREATORBUG-15639

John says:

My complain is that it is too naggy, reporting a number of “issues” for code which compiles without any error or warning.

Is there a way to disable individual warnings for it instead of disabling it completely?

Eike Ziller Eike Ziller says:

Yes, Tools > Options > C++ > Code Model > Clang Code Model Warnings

anton says:

One Question concerning QML Projects:

Is the Tree View now available in the
Qt Creator – Design tool?

In Qt Creator 3.6.1 it’s not 🙁

Thomas Hartmann Thomas Hartmann says:

The answer is no.

We concentrated on the upcoming Qt.labs.controls.

I guess what you are asking for is Tree View support at the level of the widget designer.

Can you file a bug report/feature request so this gets more visibility?

aportale says:

Thomas changed his answer to Yes 🙂 https://codereview.qt-project.org/156492/

In Qt Creator 4.0 final, TreeView is available in the item librarty, like TableView already was. There is no feature (yet?) for inserting entries (as the Widget Designer does).

Dim says:

First of all, thank you for the great improvements in CMake projects.

Meanwhile, is there any way to add custom CMake variable/option (-Dxxx=yyy) for the generation step? The project view doesn’t allow to add any.

Thunder says:

I noticed this same thing. I wasn’t able to figure where these arguments could be entered. Previously (3.6.1) you could specify these in the Arguments field of the CMake Wizard (Build/Run CMake). With 4.0.0-rc1, it just runs cmake with no where to enter any arguments. There should be a way to add these.

There are some variables on my project that I always define on the Arguments (and recent versions of QtCreator remembered these). I’ve had to modify the CMakeLists.txt files to add these variables as CACHE variables so that they show up on the Projects page under CMake. I can then set their values here and rerun CMake.

There probably should be a “Arguments” field where these can be entered on the Projects page.

Thunder says:

See https://bugreports.qt.io/browse/QTCREATORBUG-16144

Thunder says:

Turns out there is a way to add variables. Either Tools>Options>Build & Run>Kits or the Manage Kits… button on the Projects page, down under the CMake Configuration, Change… Just add the variables and values here (Variable=Value).

Bobs says:

Actually, Clang analyzer option is still disabled for me and there is still no options to enable or run it.

Configuration: Kubuntu 14.04, CMake-based project, out-of-source build. What am I doing wrong?

Ernst says:

For me , the feature is still unstable. I faced with a similar issue on my Windows host. and found interesing dependency when the analyzer is enabled and when is not: if I’m configuring my compiler kit manually via environment varisables LIB,INCLUDE,PATH, it’s disabled. if I’m using as default kit auto-configured (detected by IDE) compiler – analyzer is eneabled.

By the way, anaylzer doesn’t work for me anyway. I tried to run this on my little project , it found a few issue and reported this in command line window “Application Output” but Analyzer output is empty , seems IDE can’t recognize clang-cl correctly and parse this for the showing point by point .

and I’d prefer to see clang-tidy integrated into IDE, it includes Core C++ Guidelines checks in addition.

Christian Kandeler Christian Kandeler says:

cmake does not provide the necessary information to do the analyzing. Only qmake and qbs are supported at the moment.

Cristian says:

This statement is not completely true. I ran the clang analyzer on a cmake project.

I had the clang model enabled, the path to clang.exe set for clang analyzer.

Ernst says:

I’m also using Clang Code Model, and it works fine for me, and clang for analyzer is also has been set correctly.
when I’m starting the analyzing it works (I mean the process is started and I see the output of clang.exe in Application Output panel) , however I see nothing in Analyzer panel, at the same time when I see the errors in plain/raw output of clang call in APplication Output. so I think qtc can’t parse this and insert into analyzer results

Adam Strzelecki says:

The only pity is that the Light Flat theme that would play much better with OS X, as announced in last year, is not in this release. For some reason the dark one received higher priority, regardless of many comments favoring the light one in the last year’s post. I hope it will arrive soon in 4.1, or maybe can make it into 4.0?

Eike Ziller Eike Ziller says:

Actually the current “Flat” theme is neither dark nor light, it follows the “light with dark tool bars” pattern that the classic theme has. Light and dark variants are on the TODO list though.

Ernst says:

please fix clang analyzer feature. it’s not available/diabled in RC build. as I see from other people – on windows host as well as on ubuntu

Commenting closed.

Get started today with Qt Download now