Qt Creator and other tools

Why don't you just file a "bug report":http://bugreports.qt.nokia.com/ ?

Near the top, but that is just me I guess.

I didn't see that a binary version was available...

It fix this problem.
Thanks.

hum, hem, my bad, just needed to add an 's' to 'proc.command' (so it's proc.commands)

@Tobias Hunger
Ok thank you for the information. I thought that there is a official way to use one of the output windows, without creating a seperate window.

@Gerolf
This tutorial is very helpful but not up to date.

You can map you local CD drive to the VM or use an iso immage.

Create the virtual machine right click --> properties (or similar, I have a german one :-) ) Hard disk --> IDE controller select empty slot and then CD/DVD drive --> host you could activate Passthrough or leave the check box out...

There is "QTCREATORBUG-2443":http://bugreports.qt.nokia.com/browse/QTCREATORBUG-2443 requesting exactly this feature.

both windows machines or has the other one an other OS?

[quote author="ZapB" date="1301340439"]Try the latest beta of qt-creator 2.2. I understand that this has seen several improvements to the code model that is used by the auto-completer. If it is still broken there then please report it as a bug.[/quote]

Verified that it works in 2.1, as I'm at work, I can't verify the beta build.

I have another issue with C++ extensions.

When I register a new type to qml and import it the quick designer reffers to the import as an error.
"package not found"
So as soon as I import a new type the designer becomes nearly unusable.

Is there a way to go around this or is it still a bug ?

I've created a "bugreport":http://bugreports.qt.nokia.com/browse/QTCREATORBUG-4249

"Qt Creator -> Preferences (or shortcut cmd-comma) -> Qt4" is the menu path for that in OS X version.

I don' know, but the bug can reproduce every time

Open designer(zh_CN version4.7.0),
drag and drop one form(must need qrc file ) to window. Now pop up a messagebox: "loading qrc file". Then if I clicked "Yes" button, the window crash., or if I switch other windows, the messagebox not respose, must kill it in "windows Task Manager".

So this problem I met is not the same to "Multiple pages in QStackedWidget":http://developer.qt.nokia.com/forums/viewthread/4293. If not loading qrc file, I can open more than 15 files

Better file a bug report on http://bugreports.qt.nokia.com

bhupathirao: Please check the documentation we ship with Qt Creator: That does explain all these details.

The Deployment settings are in Project mode, Run Settings.

Thanks for all the suggestions. This is going to be just me (or predominantly me, anyway). Those services that Volker mentioned sound good, but...I'll have to schedule some time to learn them. I guess it'll wait until I've become more proficient with Qt.

Never mind, classic case of me spotting the problem a few seconds after posting the issue. Auto complete seems to have messed up the class name in the test class implementation file. Sorry for wasting bandwidth.

Ah, ok, so it is the right site. I found it but seeing the text-only pages I thought that it was a wrong link. It seems that these pages have no stylesheet on them at all... I try later. Thanks.

I'm getting crazy trying to make it work the way I think it should. I must be misunderstanding something.

I would like to have qmake generate makefiles that produce the output (TARGET) in specific directories for debug and release. I've tried something on the lines of what you (and many others) suggest, but it simply doesn't work for me.

I have:

@TEMPLATE = lib
CONFIG = qt shared debug_and_release build_all

debug_and_release:build_pass {
CONFIG(debug, debug|release) {
TARGET = ColorAnalyzerSimulator_debug
DESTDIR = debug
} else {
TARGET = ColorAnalyzerSimulator_release
DESTDIR = release
}
}
DEPENDPATH += .
INCLUDEPATH += .

Input

HEADERS += ColorAnalyzerSimulator.h
SOURCES += ColorAnalyzerSimulator.cpp@

And I issue the command

@qmake -spec macx-g++ -o Makefile.mac Simulator.pro@

and when I look into the Makefile.mac.Debug, TARGET has the default name (Simulator) and DESTDIR is empty!!

I have tried many variations of these settings but no result. I've also tried a similar thing on Linux and still no result.

I really hope someone can help.

[quote author="GordonSchumacher" date="1292262276"]Honestly, you really don't want OBJECTS_DIR to be the same between the builds either! (What happens if you inadvertently get a mixture of debug and release object files...?)

What I've done in the past is something like:
@debug_and_release:build_pass {
CONFIG(debug, debug|release) {
CURBUILD = debug
} else {
CURBUILD = release
}

DESTDIR = $${OUT_PWD}/$${CURBUILD} OBJECTS_DIR = $${OUT_PWD}/$${CURBUILD}/$$dirname($${_PRO_FILE_PWD_}) MOC_DIR = $${OBJECTS_DIR} UI_DIR = $${OBJECTS_DIR} RCC_DIR = $${OBJECTS_DIR} INCLUDEPATH += $${OBJECTS_DIR} LIBS += -L$${DESTDIR} unset(CURBUILD)

}@

I'm not positive those are all actually necessary, but you get the idea anyway.[/quote]

The default debug flags are simply "-g" which is set for QMAKE_CFLAGS_DEBUG and QMAKE_CXXFLAGS_DEBUG.