Eike Ziller

Qt Creator 3.4 beta1 released

Published Thursday March 5th, 2015
20 Comments on Qt Creator 3.4 beta1 released
Posted in Qt, QtCreator, Releases

We are happy to announce the release of Qt Creator 3.4 beta1! This release focuses more on bug fixing, polishing and under the hood changes, but nevertheless comes also with a range of new features.

We added auto-completion for the signal and slot parts in Qt 5 style connects, so you usually no longer need to look for the type manually. Just type the “&” and let auto-completion figure it out.

Locator has a new filter, All Included C/C++ Files. It finds all files that are used in your projects by including them, even if they are not explicitly mentioned in your project. The filter is part of the default that is used when you just type in the Locator input field, and shares the shortcut string with Files in Any Project.

Android integration now also supports 64 bit tool chains, and bare metal development can now also be done with generic projects. There have been many more enhancements, please see our change log for a more complete list.

Users of the Professional or Enterprise edition will be happy to hear that we added experimental integration for Qt Test based auto tests and Qt Quick tests. You get another navigation pane Tests, which lists the tests defined in your project, provides ways to run individual or sets of tests, and nicely shows test results in a new Test Results output pane. To try it, open Help > About Plugins (Qt Creator > About Plugins, on OS X), turn on Utilities > AutoTest, and restart Qt Creator.

We also moved the Clang static analyzer integration out of experimental state, and added support for using it in combination with MSVC (you need at least Clang 3.6 for this), and MinGW. You can also suppress individual diagnostics for a file in your project now.

You find the opensource version on the Qt Project download page, and Enterprise packages on the Qt Account Portal. Please post issues in our bug tracker. You also can find us on IRC on #qt-creator on irc.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 Qt, QtCreator, Releases


Guido Seifert says:

Looks better and better. 🙂
Clang analyzer is great. Though there is a little fly in the ointment, which spoils total bliss: QTCREATORBUG-12935
Buuut… great job.

Scorp1us says:

Did you fix the “” problem? Me and a bunch of others wrestle with the “” at the wrong times, and then backspace removes both “” back.

Ariel says:

No, they have not. In the mailing list I enumerated how many keystrokes are saved (few) and how many are wasted (lots). Intelligent behavior is only useful up to the point of trying to be Clippy.

Unfortunatly, you cannot disable them without disabling useful intelligent features such as auto braces.

aportale says:

We will verify whether the quoting feature still works as intended.


Eike Ziller Eike Ziller says:

One thing that I noticed, is that there is no separate undo step for the automatically applied change, which I think would be standard behavior in editors that have some sort of ‘auto correction’.

Chris Bruner says:

Will the examples be updated to show the Q5 style connects?
I’m finding that as the tech moves along and older tech is still present there are lots of choices, but I don’t always know which are the good ones. If the new connect style is the new QT standard then it would be easier if the examples reflected that.

Eike Ziller Eike Ziller says:

See the current discussion on the Qt development mailing list: http://lists.qt-project.org/pipermail/development/2015-March/020627.html and related. The content of the Qt examples don’t have anything to do with Qt Creator though.

gyll says:

“Added “Copy Path and Line Number” to context menu of document selector”
Great, so there is enough room for this menu item, but the menu would have become too long with a “switch between header/source” item. This was your argument for not adding “switch header/source” in this menu when i wrote a feature request, you went on and on with insisting that “the menu would grow too large” (duh!!!). I explained that the value of such a menu item would be that you could change between source and header without changing the cursor position when switching header/source (if you use “switch header/source” in the editor context menu you change the cursor position the moment you right click in the editor window), but you decided to just close the suggestion.
So maybe you’ll reconsider and just add a “switch source/header” item to the file selector context menu.

Eike Ziller Eike Ziller says:

Even though I think that we should indeed be careful that context menus do not grow too much, and “Switch Header/Source” is already available in Tools > C++, in the editor’s context menu, and by default as F4 keyboard shortcut, the line of argumentation in QTCREATORBUG-10614 seems to be

“The action fits much better in the context menu of the editor, as it’s related to the other code-model related navigation features. The context menu of the editor toolbar contains actions that affect the whole editor and/or work on the path of the editor. Even though Switch Header/Source does use the path, we consistently regard it as a code-model navigation feature. See for example the global menu, which has it under Tools/C++.”

Eike Ziller Eike Ziller says:

I think it could be argued that the context menu of the editor might be a better place for “Copy Path and Line Number” since it depends on the cursor position in the file, and on the editor actually having the concept of “lines”. On the other hand there is the obvious relation to “Copy Full Path” in the document selector menu, and most of our editors are text editors. (Note that most of our editors do _not_ have the concept of “header” and “source” though.)

gyll says:

There is NO VALID ARGUMENT for changing the editor’s cursor position (which is what happens the moment you right-click inside the editor) as a consequence of an action that does not require, nor intends, to change it. Period.

gyll says:

By the way, and i said this in the suggestion: if you want to have it in the editor’s context menu, fine, i totally disagree with your arguments but so be it, but then at least add it to the document selector context menu also. And this it the biggest problem i have in all this argument with your way on thinking, that you refused to add this even as an *alternative* (well, at least you are consistent, you also refuse to add tabs as an *optional* navigation function in creator).

Eike Ziller Eike Ziller says:

I would say that a change that makes right-clicking no longer move the cursor position, while still executing all context menu items in the context of the clicked position in the file, would be fine.

gyll says:

No, it wouldn’t be fine, it would be awful, it actually would do more damage than it would fix, how can you even suggest such a thing? Do you know of any professional IDE that behaves like that? It will be extremely confusing to have the action performed for another item other than than the one with the cursor. You’re ready to invent the square wheel instead of just adding that menu item in the document selector’s context menu, WITH NO REASONABLE ARGUMENT against placing it there.

HGH says:

Will you fix the Dark Theme for this release?

Eike Ziller Eike Ziller says:

That probably depends on many factors: What you think needs fixing, if there are bug reports, …

HGH says:

The project wizards are not dark for example and not displayed properly, basically nothing is visible.
Due to this I stopped using it but I will whenever it is ready. I haven’t seen any other issues because I haven’t used it much.

Gunnar Roth says:

The windows version does not show or use qch files have already configured in 3.3.2 in %APPDATA%\QtProject\qtcreator\helpcollection.qhc. in filter tab they are listed.

if i added them on my own they are shown and work but after restart all is gone again.

HGH says:

Debugging Qbs projects (breakpoints) doesn’t work. (The error message is something like: No debug build). Is this to be expected or a bug? Should I file an issue?

Commenting closed.

Get started today with Qt Download now