Eike Ziller

Qt Creator 4.8 RC released

Published Friday November 23rd, 2018
17 Comments on Qt Creator 4.8 RC released
Posted in Dev Loop, QtCreator, Releases

We are happy to announce the release of Qt Creator 4.8 RC!

Find out about what is new in our blog post about the Beta. Please prefer using the bugtracker for reporting remaining issues.

Get Qt Creator 4.8 RC

The opensource version is available on the Qt download page, and you find commercially licensed packages on the Qt Account Portal. Qt Creator 4.8 RC is also available under Preview > Qt Creator 4.8.0-rc1 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.

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

Posted in Dev Loop, QtCreator, Releases


HGH says:

No CMake improvements

David says:

Ow that QBS has been abandoned I think cmame will get more attention, so I hope.

Liang Jian says:

It there any progress toward fixing https://bugreports.qt.io/browse/QTCREATORBUG-20609 ?

Ogrev says:

Clear and widely influecing bug … the whole code editor window is colored incorrectly but QtC was moved to prerelease RC state (https://bugreports.qt.io/browse/QTCREATORBUG-21384). Nice!
Priority for such a visible bug is even NOT evaluated (but people read the bug … because it was marked the same as https://bugreports.qt.io/browse/QTCREATORBUG-21393)! QtComp should show us the rules you expect bugs to be treated … currently it is not clear … wheather this is company policy or devs are missing something in their actions.
If there were no design decision to color ‘#’-char with alternate color then problem exist with BOTH code models.

Sam says:

The bug was fixed 2 days after you posted. Looks like it should be included in the release.

Do you actively use the old code model? Just curious why?

Ogrev says:

>The bug was fixed
Not completely I think. Clang code model is still effected … but be with alt-colored ‘#’ looks not so bad as it was for qtc-code model
>2 days after you posted.
Probably because I posted here 😉 … everybody forgot about such an obvious bug.
>Looks like it should be included in the release.
Already included in snapshot 🙂 … otherwise release of QtC 4.8 would have clear disadvantage.
>Do you actively use the old code model? Just curious why?
Yeeeees. Because of https://bugreports.qt.io/browse/QTCREATORBUG-21636
And clang code model is quite slow … I still did not understand why both code models can not work together to help each other … like … while clang code model is thinking, qtc-native code model is already build and used … and as soon as clang code model is ready its discoveries are added to qtc-code model
qtc-native code model is always faster but ALSO several things are detected better
But currently advantages of both worlds can not be used … only “smart OR pretty”! 😉

Joe says:

I missed the blog post in October announcing the abandonment of QBS so I’ll comment here.

Very disappointing. After years of being told that QBS was the future build system to replace QMake (because CMake wasn’t ‘good enough’ for cross platform targets), you just abandon it?

I’d finally tasted the cool aid and moved my projects over to QBS and now it’s already a dead end solution. Fantastic. What next, QtQuick?

HGH says:

Why is it so difficult to find the standalone installers now?

CKM says:

How to provide password protection for a qt installer binary before installation starts? can we give the password protection through installscript.qs before installation window pops up?

cemal demir says:

Some Times when i copy paste Qt Creator crashed if the class defination exist in clipboard.

Abdul says:

How to use the new Cppcheck plugin?

Rich says:

Thanks for this, have been really enjoying using 4.8.
The fact you can now autocomplete constructors when using braced initialisation syntax seems like a trivial thing, but makes everyday use much more pleasant.

cemal demir says:

Qt Maintanance Tool crashed during installation in progress after all download finished.

“Corrupt installation”
“Your installation seems to be corrupted. Please consider re-installing from scratch”

Jakub Narolewski says:

Generally speaking, Qt Maintenance Tool is kind of horrible at every little thing it does.
If you have not tried this already: just follow its post-mortem advice – nuke maintenance tool’s install directory and reinstall from scratch.

For me it happens nearly every second time I try to update something with it 😛

Ogrev says:

>Qt Maintenance Tool is kind of horrible at every little thing it does.
Yes … nobody care about its issues … for example
is a clear bug … number 2 in most users-requested bugs of Installer
… but it seems it got zero attention.
And as I understand you named first requested bug
🙂 Opened in 2013! 😉 … such cases is not a big deal for “Installer Team”

I.F. says:

Qt Creator keeps getting better with every release. Please continue with Qbs, the best subsystem.

Commenting closed.

Get started today with Qt Download now