Eike Ziller

Qt Creator 3.6 RC1 released

Published Thursday November 26th, 2015
16 Comments on Qt Creator 3.6 RC1 released
Posted in Dev Loop, Qt, QtCreator, Releases

We are happy to announce the release of Qt Creator 3.6 RC1.

Since the beta, we have fixed many bugs, including an ugly, evasive crash that could happen on code completion, depending on how you used the mouse while typing function arguments (QTCREATORBUG-15275).

We simplified the activation of the Clang code model, and added a global option for additional arguments. You can for example use this to disable warnings that you do not care about, or to enable warnings that Qt Creator disables by default.

For an overview of what has changed in 3.6 compared to 3.5 please take a look at the Qt Creator 3.6 Beta1 blog post or our change log.

You find the opensource version on the Qt download page, and commercially licensed packages on the Qt Account Portal. Please post issues in our bug tracker. You can also find us on IRC on #qt-creator on irc.freenode.net, and on the Qt Creator mailing list.

Note: Starting with Qt Creator 3.6 we no longer provide prebuilt binaries for Linux 32-bit. Building Qt Creator on that platform is still supported though.

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

Posted in Dev Loop, Qt, QtCreator, Releases


Wojciech Cierpucha says:

I’ve played briefly with the clang code model in 3.6rc1. Integration with fix-its, warnings and errors is great. Marking them on the scrollbar is also something I’ve waited for. But unfortunately the model got so slow it is unusable for me. The clangbackend process is at 100% CPU for quite some time almost everytime I request a completion. In 3.5 that was the case only for the first request in a translation unit after loading it or after changing the #includes.

HGH says:

Do we have proper theme support on all platforms now?
I am hoping for a good dark theme too.

Alan says:

Same here. The current dark theme is awful. Combine that with the syntax coloring issues (eg. using inkpot to edit a shell script) and I find myselft more and more using other editors.

What ever happened to the flat theme that was talked about months ago?

Eike Ziller Eike Ziller says:

“What ever happened to the flat theme”

There have been some changes in master, with more in review and being worked on. It is a whole lot of work and not the top priority.

HGH says:

Let’s say… I use dark Theme because it is easier on the eyes and not because it is prettier.
Now that’s a top priority reason I think.

Jakub says:

There already is cool dark theme. The only thing to remember is that You have to set dark theme separately for environment (Environment->General->Theme) and text editor (Text editor->Fonts and colors->Theme)

HGH says:

Unfortunately it is somewhat crappy/buggy yet.

Jason says:

Great, In the OSX platform QtCreator finally not so easy to crush.

Danny says:

“Since the beta, we have fixed many bugs, including an ugly, evasive crash that could happen on code completion, depending on how you used the mouse while typing function arguments”

I guess I was just holding it wrong :p

martonmiklos says:

No this is a different company 😉

Danny says:

When will Creator’s project Qt wizard support QBS projects as standard?

I’ve been using QBS in all of my projects recently and have been quite impressed by it. But I still have to create them manually from the Plain C++ target.

Alexander says:

Have the issues with High-DPI monitors been fixed?

Besides that I like Qt Creator, but sometimes it could be little bit more Emcas-like even with Emacs keybindings enabled.

Kirk says:

I’m still getting the dual monitor unplug crash (very repeatable), which is supposedly fixed in Qt 5.5.0? The error message is:

QOpenGLContext::swapBuffers() called with non-exposed window, behavior is undefined

Here is a list of related bugs (1 for Qt, 2 for Qt Creator). Which issue will be the most useful to comment on/provide additional information?


Kirk says:

Note that the crash happens the *second* time I unplug the secondary monitor, and the crash happens in 3.4.2, but with no error message (maybe because it’s compiled in Release)… Qt Creator 2.4.1 does not have this problem. I can happily plug and unplug the monitor without a crash.

Jared Johnson says:

Anyone else having occasional problems removing whitespace? My backspace key is sometimes not responding when it gets to blanks/tabs. Or am I going crazy?

Commenting closed.

Get started today with Qt Download now