Since the beta release four weeks ago we were getting all hands on finding and squishing all these bugs that start nesting in a piece of software between two releases. Oh, yeah, and spring has finally arrived here, giving us Berliners sunshine at 20 degrees celsius this week 
. The beta release was already feature complete, so if you missed that one and are interested in what is new, the Qt Creator 2.2 beta release blog still gives a good overview. Most notable bug fixes since the beta were (from my view) the lots of fixes for Qt Creator’s ABI detection, but there have been many more, not less important ones (e.g. for QML debugging, Qt Quick designer, Maemo development, and more).
If you are using the Qt SDK 1.1 release candidate (our all-in-one Qt development bundle) you might wonder when and how Qt Creator 2.2 will become part of it. The answer is that the Qt SDK 1.1 will release with Qt Creator 2.1, but a short time after the SDK and Qt Creator 2.2 are out, there will be an update for the Qt SDK, that upgrades Qt Creator to version 2.2.
Big thanks to all who gave the 2.2 beta a try and us a lot of feedback!
Get the Qt Creator 2.2 release candidate here!
Subscribe RSS
You guys blog about bug correction and release candidates…
Not as exciting as Portal 2 ! Is it because of a lost of interest in Qt ?
@CDrik: No.
And when can we see the merge of Necessitas QtCreator. I have both versions on the desktop now
BTW, when can we expect the final release of SDK 1.1 ?
CDrik,
“Lost of intrests in QT”
Yeah right? Wonder why the community already has ported it too Android then?
The only one that want Qt to fail is Mr Flop and his favorite company named M….
But as a Linux developer I know Qt will survive and we already has seen alot of QtQuick apps for the new symbian phones and also the geekphone N900.
People forget the facts that Qt is used on Linux desktop too and the KDE team is planning “integrate” QTQuick in Plasma desktop. And Ubuntu is also plaing using it in nextgen Linux desktop.
I am very glad se every report ause this prove that Qt/Creator/Quick improves.
Even if some people doing everything too hurt Qt it will survive in or outside Nokia!
Should the Remote Compiler work with this release? Can’t see that in targets list. I’m using QtCreator on Mac so I’m counting on Remote Compiler to build Symbian SIS files for me…
@Tommi
The Remote Compiler is one additional component in the Qt SDK, which installs a plugin into the Qt Creator directory. It is not a standard plugin as such right now.
O.o? I don’t get the Qt comparison to Portal 2. Am I missing something or is CDirk’s post a serious case of troll fail?
If I’m going to start a new project and want to use Qt Creator 2.2, should I start now with the beta or just wait until Qt SDK contains 2.2? (I can wait a couple of weeks.)
@pat: I suppose it’s an attempt to be funny, because Portal 2 happened to have released at the same date
. Anyhow, if you want to be on the real safe side for *mobile* development, I’d suggest to wait for the updated Qt SDK bundle, because that will receive yet another round of integration testing. If you are doing desktop stuff I’d say it’s safe to go for it with the RC, or with the snapshots (which already contain a few fixes on top of the RC and will evolve into the final).
How can accommodate qtcreator for building linux kernel modules? Now qtcreator successfully build the usual makefile projects. But when building kernel modules error occurs when the make.
Makefile is very simple for exapmle:
obj-m + = alt1.o
all:
make-C / lib / modules / $ (shell uname-r) / build M = $ (PWD) modules
clean:
make-C / lib / modules / $ (shell uname-r) / build M = $ (PWD) clean
The documentation says that project settings are saved in a .user file. Can you be more specific as I can’t find this file and my project setup doesn’t get saved. Every time I start qtcreator I have to redo the build settings (Qt Version, Build Directory for debug/release configurations etc.). It also doesn’t seem to support $(Configuration) in project files anymore – which used to be set to “debug” or “release”.
The default setup is also questionable as the release and build directories are the same. Am I the only person who builds more than one configuration at a time? Every other tool I’ve ever used puts debug and release output in separate directories and given that each configuration has a directory shouldn’t the default be {build-dir}-debug and {build-dir}-release?
I’d file a bug report but this is the case with 2.1.0, 2.2.0 Beta and and 2.2.0 RC and I’m having trouble believing it could be that broken in three releases and no-one noticed? Using Linux 64 builds on SuSE 11.2.
- the binary editor seems not to reload a binary after an external change (and click “yes all” on reload-question)
- creator contacts google-analytics when having activated help, how to disable this (_not only_ for offline development) ?
@Frank: Regarding the Google Analytics, can you check under “Tools->Options…->Help->Documentation” if there are outdated com.trolltech.* packages and remove them from the list? Iirc, there was a beta version of the offline docs which by fault contained the Google Analytics snippet, but that is supposed to have been fixed. Afaik, only the online docs on http://doc.qt.nokia.com/ are allowed to contact Google, but never the ones shipped in the Qt Sdk used by the QtCreator Help.
Could Qt Creator get support for smart pointers? Quite annoying that as soon as you wrap something in a smart pointer, you lose all the method prediction capabilities.
Another thing that gets irritating is that Qt Creator shows (and navigates to!) the installed header files even though I have the project opened where those header files originated from … made it impossible for me to sanely use Qt Creator on the Qt source code.
@aportale: removing old trolltec links worked
@Robin Lobel: AFAIK the final release was expected 2 weeks after the RC release.
Found the problem. The .user file referred to is ${projectName}.pro.user and is created alongside the ${projectName}.pro file in the source directory. Somehow the file was made read-only and it seems QtCreator doesn’t check that it can successfully write this file so it quietly fails, resulting in lost settings every time you quit QtCreator.
I know, I sound like a broken record, but please, could you do something about the overabundance of tooltips? I find it really annoying and distracting from my work when I don’t know where to position my mouse pointer so that not some tooltip opens and shoves information down my throat, which I at best need only once or twice until I know what the option does or that I can press F1 to get help.
Hey guys,
I’ve been using Visual Studio, then Eclipse, then XCode 3 and recently Xcode 4.
Qt Creator is the best IDE I’ve ever used.
Enough said.
Benjamin Arnaud.
Have to agree on the tooltip issue raised by Guido – many of the tooltips in Creator are utterly mindless. Hovering over a variable pops up the the same variable name in a tooltip which is as much use as an ashtray on a motorcycle.
I was looking at some of the debugging options in the Preferences dialog and here are some buttons with their tooltips:
Checkbox: “Close temporary buffers on debugger exit” Tooltip: “Close temporary buffers on debugger exit”
Checkbox: “Switch to previous mode on debugger exit” Tooltip: “Switch to previous mode on debugger exit”
Guys, seriously?
@Danny, Guido: I agree that sometimes the tooltips show useless information, but for the editors we don’t really have a straightforward and precise way to differentiate a “valuable” tooltip. Other IDEs (VS and Eclipse, for instance) have similar issues and behavior. Perhaps we could add an option that allow tooltips to be triggered only when the Ctrl key is down… (I think NetBeans does something like that.)
> Perhaps we could add an option that allow tooltips to be triggered only when the
> Ctrl key is down… (I think NetBeans does something like that.)
This would be (IMNSHO) the perfect solution.
hi!
I have such setting that Ctrl+B is building current project i’m in (have file from that project opened in editor) – but this isn’t working now
I’ve removed Ctrl+B from Build and set it to BuildCM, but now after pressing Ctrl+B nothing happens? Am I doing something wrong or what?
@Leandro – why even have tooltips in the editor at all?
The tooltips in the dialogs for specific options can be fixed. What amused me is that someone actually wrote the code to display the same information twice – some of the other tooltips actually provide useful information.
can you plz add code formating function for qt creator
I realy miss this function from eclipse and visual studio
Most companies need to get started on web applications quickly. Is there a simple way, perhaps to get started with IDE using Access 2000 database, see if it work and then migrate to better databases. The barrier is the initial learning curve where time and resources are used without a guarantee of the final result. Do you offer this? Could you? If a manager/owner cannot get a project working in an hour, he loses interest.
The debuggers watch window still don’t support viewing the content of a variable (scalar type)
in different formats. This is really bad if you have to deal with binary data (communication protocols, …)
At least, it should be possible to set the format to hex and int. I would also like a combined
output like
0xACDCACDC (2900143324)
Binary would also be great:
1010 1100 1101 1100 1010 1100 1101 1100
The perfekt way would be user defined output like
0x%08X (%d), %32b
Meaning (printf oriented) :
%08X : 8 digits hexadecimal
%d: Decimal
%u: Unsigned decimal
%32b: binary
Can QtCreator text editor ever get an “overwrite” mode?
To replace 123 with ABC:
123[LEFT][LEFT][LEFT][INSERT]ABC
I have used Qt Creator for some time now and I appreciate most of what it does. It is generally a smooth ride and does the job well.
What I would like to comment on after a few weeks usage is
1) that Qt Designer is is a bit underconfigurable and the main environment cannot (yet?) be customised exactly to my liking;
2) and secondly, I am *hugely* annoyed by that I cannot switch between insert/overwrite character input modes. A quick search indicated to me that this apparently is kind of a religious topic to some, but to me and many other it is pure pragmatics. A feature like this is considered standard, obvious and necessary, and the lack of it simply astonishing. It is not worth making a pragmatical detail into what I suspect might be a battle of principles.