Eike Ziller

Qt Creator 4.0.3 released

Published Thursday July 7th, 2016
10 Comments on Qt Creator 4.0.3 released
Posted in Biz Circuit & Dev Loop, Qt, QtCreator, Releases

We are happy to announce the release of Qt Creator 4.0.3.


In this release we removed a bug which disabled the run button on macOS 10.8 and FreeBSD, made the Clang code model stop replacing the dot in floating point literals by an arrow, and fixed an issue with opening CMake projects from symbolically linked directories.

Please find more information in our change log.

Get Qt Creator 4.0.3

The opensource version is available on the Qt download page, and you find commercially licensed packages on the Qt Account Portal. Qt Creator 4.0.3 is also available through an update 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 Biz Circuit & Dev Loop, Qt, QtCreator, Releases


Prav says:

>Please post issues in our bug tracker
I think users who filled bugs need Qt Company to show that someone is actually reading what we posted and necessary fields are filled. Or I do not understand what is the motivation to use such Bug Tracker.

I would suggest users to make less filling of new bugs (may be only critical) until Qt Company will decide to find time to get through our already reported bugs (which means exactly for all bugs with like … 3 months or more from creation time … change its state from Reported to something else, fill fields “Assignee” and “Fix Version” ). We waste time to fill bugs for Qt but they hangs for years in the system … totally forgoten.

While seeing this strange attitude to our bugs it is so awkward that Qt waste resources on changing Logo and banners and such things. Dev are care about correctness more than Logo. And Lib – it is for Devs! So I would suggest to have in blog news like:
We decreased number of unprocessed bugs (which is Reported or Unassigned or having no “Fix Version”) 3 times. The oldest unprocessed bug was created 2 months ago.

This is the news devs really would appreciate! This is what we need about Qt’s attitude to the bugs in Qt lib and Qt Creator.

Dominik says:

I couldn’t agree more. I’m always quite surprised to see tons of new features added with every release while bugs marked as critical linger around for ages. Sometimes even when there are fixes available. It doesn’t become better when you’re a commercial customer btw. – the only plus is that you see a Reported_by_support_silver label next to the bug report.

Lilian says:

I want to worn users that use GDB remote debugging, since Qt Creator 4.0 GDB remote debugging doesn’t work any more.
If you get an error about some “tcp::0” connection problem, than roll back to an older version of Qt Creator, this should fix your problem.

Slava says:

Creator 4 is full of regressions, I am staying on 3.6 as well.

Prav says:

Especially interresting that Clang code model was made default and it gives tons of warnings all over the code. And developers did not gave gui elements to control (switch off) some/any diagnostic rules of this code-model … 🙁
At first glance it seems that Clang code model can not be switch to QtC’s one (as it was in QtC3) … it took me some days to findout that you actually can … Clang code-model is a plugin and you can unload it to get rid of these warnings 😉

I wonder why they changed version of QtC from 3 to 4? Like it is big step forward. Looks like 3.7 for me.

I wonder why it is so important for Qt to give more versions with more stuff faster and faster. May be it is better to show us statistics for how many bugs are still unfixed/unprocessed and ask clients what it is more important … fixes OR new features with like “user voice” site of MS Visual Studio?
I am not sure that most developers feel OK about bugs and would vote for new features … IMHO.

Eike Ziller Eike Ziller says:

Actually the Clang code model is still not the default, since the plugin is still disabled by default. What changed, is that the Clang code model is now used automatically if the plugin is enabled. This was done to simplify things, but unfortunately bites the people who turned the Clang code model plugin on, but turned it off in the settings. We should mention in the settings how to get back to the internal model.

The license change to GPLv3 + inclusion of the previously commercial-only features somewhat called for a major version number increase.

We have been releasing new Qt Creator minor versions 3 times a year since > 4 years now, so I’m not sure what you are referring to.

Slava says:

But that does not simplify anything! Before it was possible to change the code model engine on-the-fly in the settings, but now one has to reload the program. And clang code model in 3.6 branch works much better by the way.

Eike Ziller Eike Ziller says:

Changing between built-in and Clang code model on the fly never really worked as expected, and would be even more difficult to achieve the more tasks can actually be taken over by the Clang code model when it is turned on (so far it is only used for highlighting and completion, not for indexing and refactoring).

Prav says:

>Please post issues in our bug tracker
This system seems to be not so valuable for Qt Company. Why you ask us to use it?
QTBUG-46685 in Creator does not care anyone. And it comes from REGRESSION bug QTBUG-46812 introduced. All apps with Alt-key action are affected and … who cares?! … and I say this firstly because it is still Unassigned and secondly we hear that Qt 5.7 released but regression bug (introduced in Qt 5.2 … imagine !!! 5 . 2 !!!) does not have any attention.

I think that currently this bug tracker is like heap of rubbish, where developers who fixes bugs can not find real top priority problems. And this is because it is not a problem for Qt Company that there are many bugs which were not get through by specialists and which are only in Reported state, or are Unassigned or have blank “Fix Version” field … or Old bugs which just hangs in bug tracker (why they hangs in the same state for years long? … users who filled them have no idea).
Currently it is working like … aaa … We do not really care about Reported or Open state … or … We can assign someone or not (it does not matter for us actually) … or “Fix Version” can be filled or not … and we do not really take more priority for old Creation date (which user can wait for years with no attention).

So I see clear un-order in bug tracker. And users who wasted hours of time to describe bug and do more tests about them are really can not see that their work means/influence something (or someone).

Currently it seems that users are fooled with all this “Please post issues in our bug tracker”.

andre says:

Did you specify some device with hostname/ip and port in your kit or at least in the override parameters, or did you leave both unconfigured, i.e. are you talking about something like https://bugreports.qt.io/browse/QTCREATORBUG-16312 ?

Commenting closed.

Get started today with Qt Download now