We.
Woah, nice new features, you’ve hit exactly the ones I’ve been missing 🙂
Column editing, great 🙂
+1 for column editing. Great addition! And the rest of the change log looks great.
Great works guys!
Everyone says column editing is cool,
for my part I can’t figure out how to use it….
Is there some hidden keyboard hotkey combination ??
Hold ALT key (or Mac equivalent), drag-select a column and start typing.
+1 for column editing.
Is there proper Python support? (proper: more than syntax highlighting, i.e. code completion)
no “proper” python support
If digia no longer has any interest in putting proper Python support into QtCreator, how about adopting one of the many community efforts that have tried to do this, and make that the official Python plugin?
The current official Python plugin has been in Creator for about a year now, and all it seems it can do is highlight the def keyword, and make indentation.
The python editor shipped with Qt Creator *is* a contribution from outside Digia. Anyone is invited to pick that up and improve it.
Report it as a bug and then report it as a bug again 🙂
Sure, Apple doesn’t support C++11 on 10.6, but there are ways around this fortunately!
If you manage to compile Qt Creator (and Qt, I suppose), circumventing the restrictions that Apple put on libc++, then lucky for you 🙂
On the other hand we already removed support for Apple’s gdb in Qt Creator 3.1, so usefulness might still be limited in any case. Of course it might be possible to build a recent LLDB yourself on 10.6 too…, or to get a python enabled gdb from somewhere else.
In any case, we did and do not test it on 10.6 anymore (nor even tried to get it working there).
QML imports is not working in WIndows ! It do not recognize import QtQuick.Window 2.1
import QtQuick.Controls 1.2
import QtQuick.Layouts 1.1
import QtQuick.Controls.Styles 1.1
You likely need to re-associate your Qt versions with creator.
The code editor’s bookmarks are a mess:
1) this bug is still labeled “not evaluated” after 8 month since i reported it:
2) i can only edit the text, not the line number, for a bookmark. i have to remove and re-add all the bookmarks if they get displaced (e.g. after the file has been edited with an external editor) instead of being able to just edit the line numbers
3) having to right-click and select from a pop-up menu to move an item in the list is sooooooo 20 years ago. You already have a drag and drop-based UI in the help system’s bookmarks, so why on earth did the code bookmarks have to have a different UI? Beats me…
QTCREATORBUG-10687 is actually fixed in the 3.2 beta (the bug was accidentally not closed though)
Oh, okay. Just downloaded 3.2.0 beta and indeed it apparently works fine now.
PS
Since i brought up editing the bookmarks, this is the year-old suggestion (still labeled “not evaluated”): (I’ll add the drag-and-drop issue to it to have it all in one place)
@gyll: You need to understand that discussing your personal list of bugs in the comment section of each Qt or Qt Creator related blog post does not scale well and needlessly eats into developers’ resources, ill-affecting not only the rate at which the bugs you report can be handled, but also everyone else.
You are invited to use the input channels that are setup to handle such issues, as mentioned in the main text. In cases like QTCREATORBUG-10687 where the fix essentially amounts to swapping two lines of code you could even consider submitting a patch to codereview.qt-project.org, very likely resulting in your fix ending up already in the next nightly build.
@Andre: ” You need to understand that discussing your personal list of bugs”
I do understand that, my list of [current+previous] bugs (and suggestions) is pretty huge, i only wrote about this one in the comments on the blog post because it was eons-old, very annoying, and nobody fixed it after such a long time, but i am by no means using blog post comments to re-iterate through all my bug reports and suggestions.
PS
As for fixing bugs myself, i would do it if i’d have the time to go through, and understand, all that code in there, but i don’t. What i can do is to spend some of my time on finding and reporting the bugs, but actually fixing them is best left to the ones who wrote the code and introduced the bugs in the first place, this is how software development works if you want it to be efficient: you report a bug in a piece of code to the code developers themselves
@gyll: Maybe you did not go through _all_ your issues, but you listed _some_ in Qt Creator 3.0 rc (), Qt Creator 3.1 rc (), Qt 5.3.1 ()
Today you did not even bother to check whether your issue has been fixed before starting to comment.
This is not helpful. And nobody else does that.
Please, use the channels that are meant for this kind of communication.
@Andre:
>>Today you did not even bother to check whether your issue has been fixed before starting to comment.
Actually i *did* bother to check, but not by downloading Creator, i simply looked at the bug report and it was still labeled “not evaluated” after 3.2.0 release (as Eike mentioned in his reply). Indeed i didn’t think that somebody fixed the bug and forgot to close it in the bug tracker, mea culpa, won’t happen again.
Love these improvments!
Qt creator has become more and more usable for me over the past few versions. I use it for general c++ development not qt development and keep converting others to using it too.
I would love if the diff viewer worked with perforce natively. Would mean I wouldn’t have to use meld anymore.
Also, unique_ptr highlighting and following would help me out… I’m sure with all of the improvments that keep getting maid it won’t be long!
I also miss std::unique_ptr and std::make_unique autocompletion, but anyway Qt Creator is a very nice tool. I too talk about it every time I have a chance XD
Column editing is great. Been always wondering if Sublime Text and Vim can do that why not Qt Creator. Thank you Team.
If I’m not mistaken, Qt Creator’s FakeVIM has had support for block select mode for *quite* a long time. If this feature is supposed to be something similar, that is; I only use FakeVIM.
For those of new-ish to Qt, are there any instructions for how to install a new version of Qt Creator on OS X? I dragged it into Applications and launched it, but it complains it “can’t find a kit” or some such, and I have no clue how to solve that.
Stable Qt Creator releases are also part of the Qt online & offline installers, these set up the right things for the installed Qt version(s) automatically.
Nice work. But Qt Quick Designer is still reletively simple and crude. I have to write code in many cases. Its UI preview is very different from real running in Android or desktop.
QTCreator will now not compile on RedHat 6 Workstation as well now without updating GCC manually :z
Good work
Right, minimal supported compiler versions for compiling Qt Creator 3.2 and later are now MSVC 2010, GCC 4.5, and Clang 3.1
Thanks!
Does Qt Creator include separete qbs executable now (not only built-in)?
Yes. (afaik bin/… on Lin+Win, …app/Contents/MacOS/… on OSX)
Did you fix the clang code model support yet?
I take it that
-Creator’s internal code model is still broken for std::unique_ptr, elements returned from std::vector’s [] and at() etc
-The Clang code model is still very slow and doesn’t work anyway
?
Thanks for the work so far. But is Creator supposed to be a C++ or Qml IDE in the future? It sure looks like a ton of effort is constantly put into the Qml features…
@Xenakios
I am not sure I can follow your logic. The blog post summarizes as:
– Column Editing
– Help integration features
– Split view improvements
– C++ code model fixes
– Debug view improvements
– Add custom debugging helpers
– QML Profiler improvements
Which implies that all but one of those items are generic or C++ related. So what gives you the impression of a “ton of effort” is put “into QML Features”?
I didn’t necessarily target this particular release with my comment. The trend about C++ getting less important in Creator seems to have been going on for a long time.
Looking at the Creator commit log shows many many entries relating to Qml/Quick. Of course that doesn’t necessarily mean anything, just an observation on my part. My main point is about the future. Is Creator going to develop and fix the C++ areas (and not just for C++ development using Qt) or will effort mainly be focused on the Qml features?
“But is Creator supposed to be a C++ or Qml IDE in the future?”
Both.
I loved Eclipse + Qt Designer, please bring back the Eclipse plugin.
Creator is the most unintuitive Tool I’ve ever seen. The symbols aren’t self-explanatory, the QML types library is slow/unresponsive, and where are all the widgets (sorry, “types”) that are mentioned in the documentation (I have Qt 5.3, but can only see Quick Controls 1.1 in Creator)? Layouts vs. positioners, wtf?!
This is really a mess, hope the old widget approach will stay in Qt for a long long time…
Awesome job you guys! You really dealt with a lot of my personal pain points in this update, so huge thanks!!!
You changed something (I didn’t see anything related in the changelog) with respect to debugging on Android. Whatever you changed fixed and issue that I was having with the ping-pong debugger hookup.
Any idea what was changed?