Qt Creator and other tools

Done
QtCreator Bug (Suggestion) 3103

Thantatos: Just click on the little "plus" right of the "Qt in Path" and add a new Qt version that way. Basically all you need to do is provide a path to QMake.

No fiddling with your path necessary that way:-)

You can check the PATH creator sees in the project mode by the way: The build settings can show the complete environment exposed to the project and that by default is very similar to what creator was started with.

Well I installed Qt Creator 2.1 beta 2, and its right there in the Qt Creator root folder :)
qtcreator-2.0.93\share .. but I'm on winxp

Ok, I'll give it a try once I'll find some time :-)

it is a something about osx 1.6
my macbook pro is 1.5 so it work fine
now when i update imac osx 1.6.2 to 1.6.6 it work fine

Why should we want to worry about the encoding of the template when we can just use unicode which is a superset of all the others?

That the file generated from the template does not get converted properly when saving it is a bug indeed.

Thank you for considering to "file a bug report":http://bugreports.qt.nokia.com/ about this!

The easiest way would be to port the .ui files to the new Qt 4 format and processing them with uic (from Qt 4) in the future. See "Using a Designer UI File in Your Application":http://doc.qt.nokia.com/4.7/designer-using-a-ui-file.html in the Qt docs for the new approach.

thank you for the help,
moved most to the heap and all is fine.

Occam

I installed Qt 4.7.0, Qt Creator 2.0.1, and Xcode Developer 3.1.3.

All of them were installed from disk images.

I didn't install any of them manually.

I think that is what I was trying to illustrate. If you want to make the DESTDIR and TARGET have different values for debug and release you must define them for each like this:

[code]
win32 {
build_pass:CONFIG(debug, debug|release) {
DESTDIR = debug/app
TARGET = qttest_debug
} else {
DESTDIR = release/app
TARGET = qttest_release
}
}

However, it would be cleaner to define the shadow build paths for each rather than include in the .pro.

Now it's only "How to create a Qt Quick application" ;)
It will hopefully contain more in the future, after some polishing of existing material.

Does qt have to be rebuild for it to detect new plugins? I have been trying to get any examples of plugins to work in my Qt environment but have been unsuccessful. For instance, the plug and paint plugin example should be straight forward out the box but I can´t even get that to work. I´ve recompile the plug and paint plugins and see the shared library. I bring the plug and paint application up and I get and error during compile. It indicates ¨:: error: cannot find -lpnp_basictools¨. I tried to place the library under the qt plugin and still got no success. Please help!!!

just saw that this is already fixed and slated for Qt Creator v2.2 :)

Yes, that is definitely weird. So is this happening all the time even for clean builds?

Thanks!

ok ok ;) not so hard!

well, download the sources, for Qt 4.7.0 and creator 2.0.1, read the README and open a visual x64 cmd. It take long time... Generating debug and release in one shot don't work for me. If you want to compile in a specific directory, out of the source tree, you'll need perl in the PATH. I don't find how to patch the binaries to make a good package, without the original source tree write in the binaries... not useful in my case, for the moment.

a few questions and remarks:

openssl: I disable the option cause this lib is not installed in my laptop. I'll try later with the binaries from "slproweb":http://www.slproweb.com/products/Win32OpenSSL.html dbus: I don't know for the moment how to do. Is it possible on windows? debugging helpers: I have to go in the ...\qt-everywhere-opensource-src-4.7.0\qtc-debugging-helper dir and make it "by hand" (qmake and nmake). From the creator options ui it doesn't work, and the log said ok ?? strange, but perhaps a mistake... and don't know. debugging helper: debug a 32bits app with helpers on creator 64bits + CDB 64bits ... raise exception and don't work ? debugging helper: infact with and without helpers, in 64 bits mode in this case, I don't see what the "plus" ;) I need to read more docs eventually CDB: ok the first time it's really long to wait the loading but next times it's not so bad. from visual it's faster ok, but not so bad ;) jom is a separate package, I don't try to install it, but you can find a pointer "here":http://qt.gitorious.org/qt-labs/jom/#more I'd like to know how to do that with mingw-x64, and Windows SDK 7.1 (without visual installed), I'll try to do it in my spare time, if someone have experiences about that, post it :) It's so easy with linux... I don't understand why 64bits windows binaries are not proposed by Qt, and yes the windows way to jump 64bits is rock and roll, but Qt is cute cause of its portability and user friendly use.... I was surprised by the so many warning about conversion size_t/int in the libs sources! Ok I need to practice 64bits programming, I'm really a newbie on 64bits pitfalls, but it seems dangerous If someone have some good pointers on 64 bits programming, post them !

I'm not particularly a fan of a specific build system, but CMake seems to be usable in most cases I come across.

As far as I remember for the tab order problem it is necessary for the widget to get focus via tab. You should check "QWidget::setFocusPolicy()":http://doc.qt.nokia.com/3.3/qwidget.html#setFocusPolicy

You should set them in your custom widget's constructor. There's no need to define this in the plugin code.

Maybe that solves the buddy problem too. It's definitely possible, we've done these two back in our Qt 3 times and had no problems.

yes, it does not contain qmlviewer.

@lyuts
How can I create a backtrace an what is it good for? (Please remember that I cannot use the Debugger in QT Creator with my application, it is not able to start the application, so doing something on the command-line would be more helpful).