Today we release the Qt Creator 2.8 beta. Thanks to the 60 individual contributors to this version, it comes with a large amount of new "stuff" and lots and lots of bug fixes.
Too much to cover it all here, as always, so I'll try to highlight a few things:
You can now open new editor windows with Window > Split New Window. This opens a new window that behaves basically the same as the editor area in the main window (for example you can split this window as well). Opening a document will then open an editor in the last editor window that was active. Since this raises quite some usability questions, how things should work exactly, we want and need your feedback on how you (want to) use that feature, and what issues you have with how it works currently! So please open bug reports, or contact us on the mailing list or IRC when you find something that should work different.
C++ support in Qt Creator got lots of fixes, and more refactoring actions:
- Moving function definitions from inline in the header to source
- Assigning a method return value or 'new' expression to a local variable
- Adding declarations and implementations for pure virtual methods from the superclass (many thanks to Lorenz Haas!)
What many of you probably didn't notice is that Qt Creator 2.7 has an experimental implementation of a side-by-side diff viewer (which needed to be turned on explicitly). This diff viewer is now enabled by default and used for git version control operations. You can also diff two arbitrary files with Tools > Diff.
Git version control integration got many new features, most notably maybe that you now can do interactive rebases from within Qt Creator. But also added was support for updating submodules, continuing and aborting many operations, and a lot more. Thanks to Orgad Shaneh and Petar Perisin for all their work in this area.
Thanks also go to Sergey Shambir who contributed an editor for python code, with highlighting and indentation, and a python class wizard.
Otherwise, display of many data types when debugging with CDB was fixed, QNX and Android support received many fixes, and much, much more. For some more details you can head over to the change log, or just download and try it.
Qt Commercial customers find packages in the Customer Portal
Please use our bugtracker for reporting bugs!
Note: Something that I want to mention here to reduce the surprise: Progress information has moved to the bottom-right corner of Qt Creator's main window, with the option to hide the detailed progress information and just show a summary progress bar instead.
Commenting for this post has ended.
Looking at the change log, finally the Mode selector is hide-able. It was consuming lot of precious screen space.
Is that the huge black left-side bar ?
Yes. If you go to "Window" you will see the option "Show Mode Selector".
It's pretty nice because anyway the shortcuts for the modes are easy to remember(Ctrl + 1-7, Ctrl + R(Run), F5(Debug) and Ctrl + B(Build)) so you can hide it and get some more space...
Wow, thanks for pointing this great feature out. I definitely plan on hiding this bar and using the few keyboard shortcuts instead...
+1 for that, this makes Qt Creator more lean and even more great tool.
Thanks to everyone who worked on Qt Creator.
Awesome, hiding the mode selector is really something i was waiting for. I kept on closing the darn thing after every run.
Congratz ppl, and congratz Sergey!
Congratulations!
I'd also like to thank Petar Perisin for his great work on the Git plugin!
Right, added him too :)
Great Job! I love the new editor window :-) ...and all my colleagues, too!
Just one side note: Currently the editor windows state isn't persistent, so one has to reopen and position it on each start of QtCreator again. Further the external help window opens on each start, even if it wasn't active/opened before... But I'm sure these small issues can be solved ;-)
This beta is in many points a big step forward in usability!
Thanks a lot!
ciao,
Chris
Did you try activating Sessions?
Restoring also external windows when restoring sessions is on the todo list.
Yeah, finally i got multiple windows in QtCreator:)
However, right now that feature is not usable. Did you look at XCode? In XCode, single click on a file opens it in same window and double click opens file in a new window. It would be nice to have something similar (double click opens as usual, and ctrl+double click opens file in a new window).
The idea with "last focus frame" doesn't seems good for me when applied to different windows.
Also, it would be nice to add left panel to the new window too (maybe, hidden by default). That would allow to switch between /open/ files easier (i dislike combobox in a top of a window and never use it).
Same is for Locator and menubar (i would like to use file-specific actions from separate window, not from main one). Maybe menubar should be different from main menubar (except for MacOs).
BUG: git blame now doesn't use correct color sceme (it uses default instead of vim (dark))
BUG: diff tool uses incompatible colors with vim (dark) color scheme.
Please report bugs on the bug tracker.
Locator is planned to open on top of the current view at some point. Replicating parts of the menu for extra windows sounds like a good thing for the people who actually use the menu and are not on one of the platforms that have unified menu bar...
"ctrl+double click opens file in a new window": in which one... you can have multiple. (Also I find things like "ctrl+double click" are pretty undiscoverable.)
If you dislike the combo box you should try ctrl+tab (opt+tab on mac, hold the modifier and press tab multiple times possibly) :)
> "ctrl+double click opens file in a new window": in which one… you can have multiple.
In a new one, of course.
Also, there should be action in a menu (Ctrl+Enter?) for the same action to make it easier to dscover. Annyway, "open file, then press "split" shortcut" requires too many actions for me to use that feature.
> (Also I find things like "ctrl+double click" are pretty undiscoverable.)
Unfortunately, Qt Creator has too many undiscoverable features:(
> If you dislike the combo box you should try ctrl+tab (opt+tab on mac, hold the modifier and press tab multiple times possibly)
IMHO, it's usable when you switch between 2-3 files, in other cases it requires more too much time to find files in shown popup and switch to them (because you don't see list before you press ctrl+tab).
> > "ctrl+double click opens file in a new window": in which one… you can have multiple.
> In a new one, of course.
> Also, there should be action in a menu (Ctrl+Enter?) for the same action to make it easier to dscover. Annyway,
> "open file, then press "split" shortcut" requires too many actions for me to use that feature.
So you are talking about the situation were you don't have any split or window in the first place. Yes, we already have things like Tools > C++ > Open Declaration/.... in Next Split, which either open something in an existing other split or window, or, at the moment, split the window first if there is no split or window yet. Also opt+cmd+click in the code editor to follow links and open "in next split" like above. That can and should be extended to other places as well.
That doesn't change the situation for "use the active editor view when opening something 'normally'" though.
As another side note reg. combo box vs open docs vs ctrl+tab, most of the time when ctrl+tab is not useful, I just use locator :)
It would be nice to have a tiny button to hide/show the mode selector.
Also it would be great if the extra windows can be put back into the main window by dragging or something similar.
And another 2 cents - it would be nice if it's possible to drag files from project tree to the new window.
Is this the version to have LLDB support on Mac?
There is some kind of lldb support, yes. If it will work reliably in this version or not is still to be found out.
I can't get it to work:
dLldb stderr: /usr/libexec/gdb/gdb-i386-apple-darwin: unrecognized option
-P' dUse/usr/libexec/gdb/gdb-i386-apple-darwin --help' for a complete list of options.dLldb stderr: Traceback (most recent call last):
d File "/Applications/Qt Creator 2.8b.app/Contents/Resources...", line 17, in
d import lldb
dLldb stderr: ImportError: No module named lldb
You currently need a build of LLDB that supports the -P command line option.
I'm using the latest version supplied by Apple...
[Replying to myself, as there seems to be some strange limit on nesting here]
Yes, the version of LLDB Apple ships does not have the -P command line option. It also does not have a couple of other functions I'd like to use. While it certainly would be nice to get that working at some point of time, I won't spend time on workarounds for old versions until the Qt Creator integration is robust and reasonably complete for some version of LLDB, and right now that's the one from http://lldb.llvm.org/.
Thanks Andre I was able to get it working!
It wasn't easy. To build LLDB, even on OSX, you need to install PCRE and SWIG.
I wasn't able to get any pretty printing from the debugging helpers for Qt or STL symbols but I can step into and out of functions predictably within Creator and examine POD types which itself is a huge improvement over GDB.
Very encouraging. Thank you for your hard work.
Any more information you could provide would be appreciated!
Great whith Python support. Hope it can be extended and match PyCharm in terms of code compilation and Django integration
Thank you so much, I didn't expect 2.8 with Qt 5.1, awesome release anyway.
Thanks for the release, Awesome!
But why it is not compiled with Qt 5.0 ?
Because Qt 5.x is still too buggy to be used for any serious application development.
The Qt 5 packages include Qt Creator compiled with Qt 5. We decided to still keep the Qt Creator standalone packages based on Qt 4 for several reasons.
One is to have a "backup solution" for people who do experience problems with the Qt 5 based version. For example even with a "perfect" Qt 5, people would not get their fancy system style with Qt Creator on Linux, because these are Qt 4. And Qt 5.0 certainly is not perfect ;)
Also, since we still want to support compiling Qt Creator with Qt 4 (e.g. interesting also for Linux distributions), it makes sense to have a Qt 4 package too. It also is a good showcase and test that it is possible to slowly transition from Qt 4 to Qt 5 with your apps (something that we have learned from the Qt3 -> 4 transition).
We will most probably completely switch Qt Creator over to Qt 5 in one of the next versions.
Yes I've used the version of Creator supplied with Qt 5 and it was very buggy.
e.g.
https://bugreports.qt-proje...
https://bugreports.qt-proje...
Please support qt 4 as long as possible. Our product release cycles demand we support our qt 4 based product for at least the next 5 years. While we probably will got to qt 5 someday it won't be now, and I'm trying to avoid the disk space required for several versions of qt libraries.
[I think it's clear, but for the casual reader explicitly: This is about building Qt Creator itself with Qt 5, not about restricting its ability to build projects using Qt 4 (or Qt 3, or no Qt at all for that matter).]
One of the original reasons to have Creator at all is to have a non-trivial in-house application that can serve as a test bed for Qt itself, before it is released. Creator has served well in this role in the past by catching scalibility issues that do not show up in the small examples typically created along with new Qt code, or issues that simply did not show up during normal testing, or only in conjunction with other features.
Keeping the source base compilable with Qt 4 would cut is off more and more of the new Qt 5 features, which then don't get this kind of "reality check" anymore.
I understand your concern about diskspace, but it has to be weighed against other concerns.
Yes, please support 4.8 as long as possible. I use Qt Creator over Nx Client, and it works much better with "-graphicssystem native" - and Qt5 does not support this. :-(
Nice release. Love it!
Thanks you guys!
YOU ARE THE BEST!!! Multiple Window. Now i can buy more monitors! :D
Yes finally!
I wanted multiple windows for so long!
I'd use them with virtual desktops. On one, I'd have the header file and the implementation file side by side. On another I might have the implementation file beside some documentation.
This is going to be great!
This is an awesome release! Thank you!
It fixes a bunch of little annoyances I have had for years now and adds some great new features I didn't know you were even planning.
One thing I would love to see would be the option to have application output alongside the file editor instead of underneath it. Screens these days, particularly on laptops, are short and wide compared to how they used to be. With side-by-side output and code I'd be able to have more lines of each on the screen at once which I would find much better for debugging. That sort of flexibilty is about the only thing I like about Eclipse...not enough to make me swap from Qt Creator, but I look at it wistfully, sometimes.
Being able to hide the mode bar is nice but there needs to be a UI for changing modes without showing it again. Maybe menu actions somewhere or a combo box in the bar at the lower right left of the "progress" indicator.
Speaking of which, the progress indicator really could use some work. it's either 0%, 50% or 100% on my computer. In other words it does not indicate progress at all. :-(
Split window support really is great through. Once all the details are ironed out it will be awesome. I 2nd the request to be able to pull files out into separate windows, or pull them back in, similar to how you can do that with tabs in Chrome.
> Being able to hide the mode bar is nice but there needs to be a UI for changing modes without showing it again.
Ctrl + N ...
> it's either 0%, 50% or 100% on my computer. In other words it does not indicate progress at all.
Unfortunately that's a qmake limitation, which does not report progress at all.
"N" being a number of course ;)
Maybe I wasn't clear. I'd like to be able to more easily discover and toggle the visibilty of the "mode selector", aka the giant side toolbar that is rarely used outside of switching between edit mode and the debugger. :-) I'm well aware of Cmd+0-6 on Mac. That said, a keyboard shortcut is not a visible UI for toggling the side bar. Yes there is a menu action (Window -> Show Mode Selector) but what I'm looking for is a tiny icon that is visible within the Qt Creator UI without requiring too much space. As an example, in my Qt application we have a side toolbar that can be minimized by clicking a tiny disclosure triangle at the top of the side toolbar.
http://www.snapgene.com/pro...
Ok, that was not clear to me indeed. I was thinking of making the current "hide sidebar" button a three state button, switching between modeselector+sidebar, modeselector, none (but keeping the menu items + shortcuts separate)
Again congratulation on being able to hide the mode bar. Is there a way to hide the below bar too? My purpose here is to make Qt Creator as lean as possible in some circumstances where one does not need full screen mode but a lean (less destructive) Qt Creator.
Please, stop doing your own bicycles, just look on visual studio 2012 and do windows like in studio. In VS you can combine all windows like you want. Seriously just look on VS. So VS windows ideology + Qt crossplatform = Awsome crossplatform IDE.
People need to stop holding VisualStudio up as some kind of gold standard. It's a poorly designed, bloated IDE.
VisualStudio's windowing system is terrible. There are too many tabs and it's too easy to screw up your workspace by accidently dragging one of them and docking it somewhere else. Plus the default setup is idiotic.
Windows layouts are saved separately for editing and debug so you have to setup your preferred workspace twice.
Seriously I spend more time fighting VS and it's windows than writing code.
Creator is sooooo much better.
Completely agree. I used to work in Visual Studio and have loved migrating to Qt Creator. It's much leaner and can be customized in just the right ways.
VS gives more abilitys to customize all windows how u want, and on monitors where u want. So then I debug my source code on one monitor and call stack on another monitor. Btw many peoples uses VS and many peoples who uses VS say's: its be good if this IDE be crossplatform.
But I undestand u. Realization of windows system like in VS 2012 hard to create by widgets that exist in standard template of Qt.
You could implement something similar with Qt without too much work.
But that would be a bad idea.
I assume you're referring to Visual Studio 2012? The release with the eye-bleeding tiny black and white icons and ALL CAPS menus that has been universally panned by everyone forced to use it?
You really want to hold up that mess as the standard?
Like I say in higher posts, peoples like WINDOWS system like in VS 2012, its very customizable! I dont say about "ALL CAPS" menus.
BTW black theme of VS 2012 is very good theme.
Did Qt Creator already get ability to change background without hacks of left panels where projects and opened files ?
Interesting to see Python support included/improved. Does this signal Python becoming more of a first-class citizen with regards to Qt? And possibly more active development on PySide?
As far as I know there is no roadmap for python support from the Qt Project's "core team", but you might be better off asking on the Qt development mailing list (or one of the other channels).
Request a "hide menu" option. Cause of awesome locator I am almost never use top window menu and want to use this space for one additional line of code instead (specially on laptop). I believe it is not hard to implement an optional firefox-like behavior: by default menu is hidden and it appears when "alt" is pressed.
> This diff viewer is now enabled by default and used for git version control operations.
How to disable it and return old diff viewer? :)
Check off Preferences > Version Control > git > Use diff editor (or something like that, in newer builds it is "Show diff side-by-side"
It would be awesome if all version control functions (e.g I'm still using SVN) allowed you to switch between inline and side-by-side diff viewers the way gitorious does. That would be awesome!
I like the new git diff viewer, however I'd find it much more useful if one could make changes to the diffed files (e.g., replace a text block in one diffed file with the corresponding text block in the other diffed file).
Put something like Qt Creator 2.8 (standalone or Qt) in the shortcut. Because when a second one is installed (one always come with Qt and it cannot be uninstalled), Windows displays two shortcuts (Qt Creator) which are indistinguishable.
It would greater if it has support to add the source in a specific directory instead of doing it all by my own, like a real project manager, no just and IDE. Nevertheless, it looks great, keep going, guys.
You can run 'qmake -project' to create a dummy .pro file, and open that. [And yes, I know that building a project typically requires a bit more than 'throw all files that look like sources on a compiler', but the dummy project is usually good enough for code navigation, and can in simple cases even used for building]
A half-finished python script for converting color styles from studiostyl.es to almost-usable styles for QtCreator.
https://gist.github.com/ano...
what I used for windows split:
split: Ctrl+W, Ctrl+Down
split SideBySide: Ctrl+W, Ctrl+Right
RemoveCurrentSplit: Ctrl+W, Ctrl+Del
splitNewWindow: Ctrl+W, Ctrl+Up
FollowSymbolUnderCursorInNextSplit: Ctrl+W, Right
JumpToFileUnderCursorInNextSplit: Ctrl+W, Right
and I think openInNextSplit is not enough, What I expect:
FollowSymbolUnderCursor In RigthSplit: Ctrl+W, Right
FollowSymbolUnderCursor In TopSplit: Ctrl+W, Up
FollowSymbolUnderCursor In LeftSplit: Ctrl+W, Left
FollowSymbolUnderCursor In DownSplit: Ctrl+W, Down
and another wish:
I can drag & drop one file title to another split window , and duplicate dragged file to open in dropped split window.
since QTCreator 2.7 I'm having severe problems while debugging with cdb. Everything fine with 2.6.2 but since 2.7 nothing seems to reliably work :-(..
Are those problems still present in the 2.8 beta? And which problems are we talking about?
There are a lot of exceptions while debugging and once while debugging an if-condition that should be true (and was true when executing it without debugging), the debugger apparently jumped into the false branch. The whole debugging seems to be very strange und not reliable. Debugging the same project with Qt Creator 2.6.2 works great, but not with 2.7 or 2.8... I cannot believe that I'm the only one with grave CDB debugging problems!?
The 'debugger jumps into the false branch' cannot be caused by Creator, as Creator does not do the jumping itself, but instructs CDB to do 'one step', and asks CDB for the 'current' location after that step. If you end up in the wrong branch, it's pretty likely eaxtly what's happening in reality in your code (and with a very, very small probability the result of the compiler creating wrong debug information, or CDB mis-reading correct debug information)
Well, the behaviour is really strange. I believe you, that QtCreator just shows, what CDB is doing, but I assure you, that if I run the application with QtCreator 2.6.2 CDB jumps into the true branch and with QtCreator 2.8 it jumps into the false branche, which is wrong if I have a look at the values that are evaluated in the condition. I have no idea why this is happening.. I tried to reproduce the problem with a simple example, but in this example there is an exception after stopping at the breakpoint ("write access violation"). I've written a bug report for the example: https://bugreports.qt-proje...
What kind of exceptions do you mean?
Is the problem with the if condition reproducible?
With hidden mode-bar, I am now missing an indicator of whether the application is currently executing (or in debugger) in the edit mode.
Another option might be to show the mode-bar when hitting the left application border and hiding it again once the mouse has left it.
In my experience/opinion these kind of "show when mouse hits border" behaviors only work for fullscreen apps. Otherwise the hit-area is either too small, or so large that it's annoying when trying to use the UI next to it.
Hello,
I just downloaded the Qt-Creator 2.8.0-Beta source and try to compile it on my MacBook Pro. But I get compile error using qmake -r and make:
clang++ -c -pipe -mmacosx-version-min=10.6 -O2 -Wall -W -fPIE -DIDELIBRARYBASENAME=\"lib\" -DQTCREATOR -DQTNOCASTTOASCII -DQTDISABLEDEPRECATEDBEFORE=0x040900 -DQWEAKPOINTERENABLEARROW -DQTNODEBUG -DQTQUICKLIB -DQTWEBKITLIB -DQTQMLLIB -DQTWIDGETSLIB -DQTSCRIPTLIB -DQTNETWORKLIB -DQTCONCURRENTLIB -DQTGUILIB -DQTV8LIB -DV8SHARED -DUSINGV8SHARED -DQTCORELIB -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/mkspecs/macx-clang -I. -I../../../../src -I../../../libs -I/Users/guohaode/qt-creator-2.8.0-beta-src/tools -I../../../plugins -I../../../../share/qtcreator/qml/qmlpuppet/instances -I../../../../share/qtcreator/qml/qmlpuppet/qml2puppet/instances -I../../../../share/qtcreator/qml/qmlpuppet/commands -I../../../../share/qtcreator/qml/qmlpuppet/container -I../../../../share/qtcreator/qml/qmlpuppet/interfaces -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtQuick -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtQuick/5.0.2 -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtQuick/5.0.2/QtQuick -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/lib/QtQuick.framework/Versions/5/Headers -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtWebKit -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/lib/QtWebKit.framework/Versions/5/Headers -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtQml -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtQml/5.0.2 -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtQml/5.0.2/QtQml -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/lib/QtQml.framework/Versions/5/Headers -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtWidgets -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/lib/QtWidgets.framework/Versions/5/Headers -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtScript -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtScript/5.0.2 -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtScript/5.0.2/QtScript -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/lib/QtScript.framework/Versions/5/Headers -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtNetwork -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/lib/QtNetwork.framework/Versions/5/Headers -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtConcurrent -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/lib/QtConcurrent.framework/Versions/5/Headers -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtGui -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtGui/5.0.2 -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtGui/5.0.2/QtGui -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/lib/QtGui.framework/Versions/5/Headers -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtV8 -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtV8/5.0.2 -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtV8/5.0.2/QtV8 -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/lib/QtV8.framework/Versions/5/Headers -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtCore -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtCore/5.0.2 -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtCore/5.0.2/QtCore -I/Users/guohaode/Qt5.0.2/5.0.2/clang64/lib/QtCore.framework/Versions/5/Headers -I.moc/release-shared -I/System/Library/Frameworks/OpenGL.framework/Versions/A/Headers -I/System/Library/Frameworks/AGL.framework/Headers -o .obj/release-shared/graphicalnodeinstance.o ../../../../share/qtcreator/qml/qmlpuppet/qml2puppet/instances/graphicalnodeinstance.cpp
In file included from ../../../../share/qtcreator/qml/qmlpuppet/qml2puppet/instances/graphicalnodeinstance.cpp:1:
In file included from ../../../../share/qtcreator/qml/qmlpuppet/qml2puppet/instances/graphicalnodeinstance.h:6:
In file included from ../../../../share/qtcreator/qml/qmlpuppet/qml2puppet/instances/objectnodeinstance.h:34:
In file included from ../../../../share/qtcreator/qml/qmlpuppet/qml2puppet/instances/nodeinstancemetaobject.h:36:
In file included from /Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtQml/5.0.2/QtQml/private/qqmlvmemetaobjectp.h:68:
In file included from /Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtQml/5.0.2/QtQml/private/qqmlcompilerp.h:61:
In file included from /Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtQml/5.0.2/QtQml/private/qqmlenginep.h:58:
In file included from /Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtQml/5.0.2/QtQml/private/qqmltypeloaderp.h:69:
/Users/guohaode/Qt5.0.2/5.0.2/clang64/include/QtQml/5.0.2/QtQml/private/qqmlbundlep.h:76:14: error:
flexible array 'data' not allowed in otherwise empty struct
char data[]; // trailing data
^
1 error generated.
make[4]: *** [.obj/release-shared/graphicalnodeinstance.o] Error 1
make[3]: *** [sub-qml2puppet-makefirst] Error 2
make[2]: *** [sub-qml2puppet-makefirst] Error 2
make[1]: *** [sub-tools-makefirst-ordered] Error 2
make: *** [sub-src-make_first-ordered] Error 2
I use Qt 5.0.2. I want to enable qml2puppet. But the binary of Qt-Creator does not support it.
Can anyone tell me how to compile the Qt-Creator or is there any binary with qml2puppet?
Thank you.
Kudos for fixing the completions when 'using Foo::Bar'! It's been bugging me for years, and now it's over :)
Hear hear!
Howdy just wanted to give you a quick heads up.
The text in your content seem to be running off
the screen in Chrome. I'm not sure if this is a formatting issue or something to do with web browser compatibility but I figured I'd post to let
you know. The style and design look great though!
Hope you get the issue fixed soon. Cheers
One very useful think with the new window split that I see missing, and for me would be super useful is:
follow the link in a new window split, just like you have option to follow link in split, but split would be opened in a new window just to not lose the current context a have a peek what does for example function do.
One very useful think with the new window split that I see missing, and for me would be super useful is:
follow the link in a new window split, just like you have option to follow link in split, but split would be opened in a new window just to not lose the current context a have a peek what does for example function do.