[/caption]
While we were stabilizing Qt Creator 2.1.0 for the Qt SDK, we were already heavily working on the features and fixes for the next version. So we are able to proudly present a feature complete beta release of Qt Creator 2.2 today. Of course this release is overshadowed by the death of our beloved polar bear, Knut, so, in memory of him this release is codenamed "Knut Creator".
Qt Creator got a range of useful new features, and a huge number of big fixes and improvements. Let me start by thanking our contributors, especially Hugues Delorme who implemented Bazaar VCS support, and Nicolas Arnaud-Cormos who contributed support for recording and playing text editing macros.
Some of you might use different source or header file extensions than what we decided to support as 'standard'. Qt Creator 2.2 has some good news for you: A new preference page (Environment->MIME Types) has been added where you can change or add mime type definitions known to Qt Creator and what editor type is used for them.
We added configurable snippets to the editors, already coming with a range of predefined C++ and QML snippets and allowing you to add your own through Preferences->Text Editor->Snippets. It supports placeholders that you fill in when inserting the contents of a snippet into your code or text file.
If you have other tools that you regularly use when working with Qt Creator, you should have a look at the new "external tool" integration. You can add menu items to Tools->External, defining the command to execute, command line arguments, standard input to pass to it, and what to do with possible output of the tool. For this you have a range of "Qt Creator variables" available, like the file path of the current document. As examples the previous Edit->Advanced->Open in External Editor has been moved to this new mechanism, as well "Sort Selection". If you miss variables or other things there, please don't hesitate to post suggestions through the usual means (bug tracker, mailing list, irc).
Debugging also got a whole range of improvements and fixes. The CDB engine received some love, and the reworked engine has much improved startup times, especially for consecutive debugging sessions on the same project, and allows you to debug 32 bit and 64 bit applications independently from how many bits Qt Creator has been compiled for. The debugger tool tips are now pinnable. For debugging on Symbian devices we now support the use of the new CODA debugging agent (no more "General OS related error" :) ), have a look at the documentation for how to turn that on. Also, mixed QML/C++ debugging got a big update.
The list goes ever ever on, with a real whole lot of fixes and improvements to QML coding support, tool chains to being configurable manually (a surprisingly big refactoring), a valgrind based mem check integration added (Debug->Analyzer) for Linux and Mac, an editor for GL shader language, real quoting and shell syntax when specifying program's command line arguments, .... .
Check the more complete list from our change log, or simply get the package and try for yourself!
Commenting for this post has ended.
I'm a debugging agent now? Fun!
Excellent ! Good job!! I can't wait to try the bazaar and valgrind support!
Fantastic, thanks very much!
Thnks!
Is it any documentation available that lists what hotkeys are supported to manipulate snippets (what hotkey to expand snippet, to move from next and previous placeholder etc)?
Hello!
Just tried the new Qt Creator 2.2 beta, and noticed some problems with deployment (to my N900 device) when selecting to skip packaging step. The process fails to copy the compiled binary to the remote device (e.g., to /opt/TestApp). Should this feature work ok in this beta version?
@Grigory - You can trigger the snippets in the same way you do for code completion (the list will show everything together but with different icons). Then you can use tabs to iterate over the snippets variables.
You can find the documentation in Qt Creator's manual under Using the Editor -> Completing Code.
download and use !
@Leandro - Thanks! Snippets works superb, except the weird snippet trigger. All snippets implementations i know (original textmate, snipMate for vim, yasnippet for emacs, zen-coding for whatever) use TAB character to expand snippet. And Qt Creator use ctrl-space to show completion window and than you need to select snippet with arrows O_O. This looks very strange to me - snippets are good for coding speed, and making it so many clicks to insert snippet reduce the speed alot. Maybe you know, is it (ctrl-space) a temporary solution and Qt Creator will bring us a TAB snippets trigger in the future, or it is some reasons for using Ctrl-space as the one and only snippets trigger?
Hello, I'm still with 2.0.1. I'm concerned about the code completion when using lots of templated stuff (like boost::spirit) which makes the use of QtCreator impossible (freezes of many seconds).
I saw on some mailing list that you were working on that issue, but I saw nothing in the different changelog. Did you work on it?
But big hooray for Valgrind, snipsets and debugger improvement
@Tristram There's been work done on it for 2.1 already. The only way to really know if it's fit for your purpose is to give it a try :-)
Will it be included in Qt SDK 1.1 final ?
All right! I overcame my dramatic lasy-ness and tried it. It seems much more reactive. Thanks a lot !
Thanks for this wonderful IDE.
I use to work with the latest QtCreator snapshots but unfortunately, the mix of QML/C++ debugging still doesn't work under Windows XP (the check box in "Build settings"=>qmake=>"Link QML debugging library" is checked). Will it be fixed for the 2.2 release? Does anyone has been able to debug QML/C++ with this version? (You can try to test this feature using minehunt demo for example)
Anyway QtCreator is really great!
When opening a .pro file, I get: "No valid Qt versions found"
My Qt 4.7.2 is configured but shows: "Failed to detect the ABI(s) used by the Qt version."
Mac OS X 10.6.6, no problems with any previous Qt Creator releases.
Am I missing something or should I report this as a bug?
@Drew, yes please create a bug report.
@Robin Lobel, the current plan is that 2.2 will ship after the SDK 1.1 and thus be available as a update for the SDK.
@Daniel Teske: OK, QTCREATORBUG-4212 it is.
Debug->Analyzer
Yes! Keep it running. I would love to see something like Apple's Instruments.
I also encounter the same problem " No valid Qt versions found"
The Qt SDK 1.1 replace the old Qt Sdk and Nokia Qt Sdk? I have understand that Nokia Qt Sdk became the final 'solution'...
Based on Qt 4.7.4? Wow
@Sylv: Did you follow closely the steps outlined in http://doc.qt.nokia.com/qtc... ? That is, recompile after checking the box in the qmake step, and also checking the mark in the run settings? We've been testing this quite extensively, so yes, that should work :) If you still can't get it to work, please create a bug report including the content of Application Output and the Debugger Log (Window->Views->Debugger). Or grap me on irc (freenode/#qt-creator).
@Stuk: Don't care too much about names ;) Qt SDK 1.1 is the one to rule 'em all. Also, Qt Creator 2.2 should compile fine even with 4.7.1, where did you get 4.7.4 from?
@kkoehne: The about dialog of Creator from the Linux 32-bit package says "Based on Qt 4.7.4 (32 bit)" (which I think is fine).
And the lib/ directory in the installation folder contains libQt*.so files in 4.7.1, 4.7.3 and 4.7.4 versions, which I find a bit strange. Is that intentional, or is the build directory on our build machine not cleaned up properly?
Lookin' good :)!
A couple of questions:
-will the upcoming release work with the latest XCode (4) toolchain on Mac (as I understood, XCode has a new compiler on it )?
-will the Assistant be back on the upcoming SDK on Mac (I'd like to meet the genious who's idea was to remove it in the first place ;))?
-will the Qt Demo be back on the upcoming SDK on Mac (I'd like to meet the genious who's idea was to remove it in the first place ;))?
It would be great if they would introduce Drag and Drop of the files in the project. To take the files .h and .cpp and drag into the projects and it automatically to arrange the .h to headers and.cpp to their location like Visual Studio does...
@kkoehne
I strickly followed the steps you've mentioned and I've already created a bug report QTCREATORBUG-4156. Maybe I've done something wrong but I really don't know what. I can debug qml ui projects, but no qml in a QtQuick QML/C++ app.
QT Creator has become my favorite IDE. Keep up the great work!
@JuhaniR: Neither Assistant nor Qt Demo were ever part of Qt Creator.
@aportale: Yes in about is qt 4.7.4 and in the /lib folder in windows there is a 4.7.4 lib, this is strange...no?
Good Job Big
@29Stuk @aportale: The answer is really simple: Due to technical reasons (qdoc changes to be specific) we had to compile Qt Creator against Qt 4.7 branch, which currently identifies itself as 4.7.4. The older libraries on Linux slipped my attention, but Creator is in fact using the most recent version. I fixed the issue in the latest nightly builds.
I've lost the ability to create Symbian target with this version of Qt Creator.
I used nightly build of Qt Creator (qt-creator-win-opensource-2.1.81-201102190108-setup.exe) with Qt SDK 1.1 Beta before upgrading and everything worked. Now I still have Symbian versions of Qt listed in Tools -> Options -> Qt4 but when I go to Projects -> Targets and try to add a new one I can select only between Desktop, Qt Simulator and Maemo5 targets. Any help?
@Daniel Molkentin:
I know that neither Assistant nor Qt Demo were ever part of Qt Creator, I've used Qt for several years :). I didn't claim that they were.
But they were part of the bundled (binary) package, which included Qt Creator, other Qt tools and Qt SDK. Someone must have made an effort to remove both, it would be nice to get some arguments why the decision was made.
Consider Assistant...it is a question of ergonomics, on a big enough display and dual display systems it eases the development to keep the documentation open on Assistant. There is no need to shuffle between the project view and the help view on Qt Creator. Without Assistant, the developer has to leave whatever view she/he was working on to get to the online help. Too much integration gets easily disturbing instead of helping the developer in his/her work.
Qt Demo on its part provides a comfortable view to the examples and demos with a nice path to the related documentation.
I suspect this may have already been answered, but if so I can't find it... any news on improving debugging with MSVC? With my Git build as of a few weeks ago, it's both horrendously slow and only semi-functional (mainly I have noticed that "step to next line" does something more like "step to next instruction" or something; it often takes eight or ten "steps" to reach the next line of code).
Can you add C++0x semantics parsing to Qt Creator?
@JuhaniR: I experience no problems with Qt Creator and the tool chains from Xcode 4
@JuhaniR: I'm told by the SDK people that Assistant will be added for the Qt SDK, it is not planned to include Qt Demo
@Eike Ziller:
Thank you very much for the information :).
@Grigory - We use ctrl+space because the snippets are triggered together with the code completion options. Currently there are no plans to change it. Notice, however, that in general you can still insert the snippet in one go. All you have to do is to create a unique trigger for it (we only show the popup if there is more than one option available for a particular trigger or if there's context-aware completion available).
@JuhaniR:
You can also display the Qt Creator Help in a separate help window. The following is from the Qt Creator Manual (http://doc.qt.nokia.com/qtc...:)
"You can specify that the help always opens in full-screen mode or is detached to an external window. Select Tools > Options... > Help > General Settings and specify settings for displaying context-sensitive help in the On context help field. To detach the help window, select Always Show Help in External Window."
@Grigory:
I looked at the code completion topic (http://doc.qt.nokia.com/qtc...) and noticed that it does, indeed, seem to say that you must use Ctrl+Space. However, you actually do use Tab or Enter/Return to complete the code and the Ctrl+Space is just a way to bring up the list of suggestions if Qt Creator does not do that automatically. We'll fix the documentation to make this more clear.
Hi,
I have just downloaded Qt Creator 2.2 beta. It looks great, but:
I have 4 different versions of Qt installed in my machine, currently we work with Qt 4.5.3, in ToolsOptionsQt4 in Helpers section if I click on details I see "Gdb Helper: Not needed" but I cannot see the QString value printed in debugging.
Can you help me?
Thanks
Is there a support topic or alike somewhere?
After installing Qt Creator 2.2 on 2 machines, I have twice the same problem when trying to compile for 4.7.2 Symbian^3:
processbegin: CreateProcess((null), sbs -c arm.v5.urel.gcce44_1, ...) failed.
make (e=2): The system cannot find the file specified.
Looks sbs specific as compilling for 4.6.3 Symbian^1 works ok
@Leena Miettinen:
Leena, thank you for the information, seems to work.
However, this always requires opening Qt Creator to get the help open...also in the case when one might be working with the Designer or the Linguist.
But what bothers more, is that the separate help window of the Qt Creator isn't really up to the Assistant, as a help viewer. In Assistant, Contents, Index and Bookmarks are easily available as is the case with Search and advanced search-functionality. Plus I prefer the tabbed view.
Ok, nevermind.
Coming from Qt Creator 2.1 for the SDK, the QT4 SDK configuration for "SBS V2 directory" contains, e.g., "C:QtSDKSymbiantoolssbsbin".
Going to 2.2, Creator adds "C:QtSDKSymbiantoolssbsbinbin" to the PATH for building (note the double "bin").
Solution is to edit the SDK config and specify "C:QtSDKSymbiantoolssbs" for SBS directory.
Should I open a ticket for this?
@koying: Bug reports should go to bugreports.qt.nokia.com. Thanks.
Have you fixed the issues with the Wacom Mouse not working in Qt/Qt Creator?
Curent versions of Qt Creator does not appear to work well with non-Qt console applications. The debugger does not stop at breakpoints or the app cannot be started. Qt Creator cannot find the working directory, etc.
Andreas,
this should definitely work (and does here). Please file a bug at bugreports.qt.nokia.com, giving as much details as possible.
Hi, there. So is the tool chain support in 2.2 beta pretty final? No major design changes, etc. would go into 2.2, correct? Thanks.
@JS: The gdb helpers are only needed for older versions of GDB. Without knowing the details of your setup (platform, debugger version used), debugger log) it's hard to guess what the issue is for you. I suggest you file a bug at http://bugreports.qt.nokia.com , or contact us on freenode/#qt-creator (Europe office ours).
external tool support is nice, but it doesn't seems to support running two+ executables back-to back.. (and using Any plan to support that? Thanks.
QtCreator ---- BEST --- IDE
many thanks to all developers ...
@mig: Your comment seems to be cut off. I don't know what you mean with "back-to back". For more complex things you should probably create a shell script that does what you want and run that as an external tool.
Hello all.
I have some question. How I can add debuger to new QT Creator 2.2 ???
I downloaded QT SDK 1.1, then install QT Creator 2.2. But now in QT Creator 2.2 I must add debuger ? How I can do it ?
Regards.
Great work!!! I'm delevloping on a Kubuntu and it's definitly the best IDE :-)
Thx for the great work and OS!
Still missing a class browser. :(
@Oliver: You mean the "Class View" is lacking features to be a "class browser"?
Great Work, Keep Going Qt., We Love You Qt.,