Qt Creator and other tools

the widgets are added to your ui class, you can access them via the ui pointer or member variable:

@
// pointer
ui->pushButton->setText("bla");

// member variable
ui.listWidget->clear();
@

If you want to ensure to get answers from troll, file a bug report. some of the trolls are around here, but not all.

Go to the "public bugtracker":https://bugreports.qt.nokia.com (aka Jira), create an account and then open a new issue. Select "Qt Visual Studio Add-In".

Please make sure that you have searched the bug database for your issue, just in case someone else did already report the bug.

Maybe "QTVSADDINBUG-90":https://bugreports.qt.nokia.com/browse/QTVSADDINBUG-90 is relevant for you.

Solved!
Well, at least I can build my Qt test project with Visual nmake/cl.exe.
The problem was in the generated Makefile.Debug file.
I created a test project in my installed Visual Studio 2008 Express and compared the MSVC build command with the qt Makefile build command. I then made following changes in the Makefile.Debug:

Removed alot of defines and added a few. Changed include path from relative to absolute Removed most include paths, just kept the necessary ones Added a bunch of Windows static libs (kernel32.lib user32.lib just to mention a few) Changed "-D" and "-I" to "/D" and "/I" for defines and include paths respectively. Dunno if that really is needed, but so it was in my MSVC project...

The question is how to create the Makefile.Debug with qmake so it works from the start?

"Try this":http://lmgtfy.org/?q=c+++comment+remover

Hmmm... OK, one solution (bit of a hack, but ok) is to use this implementation of the createWidget() method:

@
QWidget *CheckBoxSpacerWidgetPlugin::createWidget(QWidget parent)
{
MyWidget resultWidget = new MyWidget(parent);

QWidget* pw = parent; while (pw) { qDebug() << "parent class:" << pw->metaObject()->className() << pw->inherits("QDesignerWidget"); if (pw->inherits("QDesignerWidget") ) { //this one seems to be only used in Design mode-- //the m_inDesignerModeFlag is private in the widget, but the plugin is a friend class of the widget resultWidget->m_inDesignerModeFlag = true; break; } pw = pw->parentWidget(); } return resultWidget;

}
@

Thank you very much for the answer. I need one little more precise definition. Where does it looks for the .vimrc? Particularly, in Windows (it's on my job).

The QML helpers are part of Qt Creator, so no extra download is necessary.

Please consider "filing a bug report":http://bugreports.qt.nokia.com/ about your debugging issues.

OK, I've discovered a partial workaround. Not perfect, but helpful. Adding an iterator for the vector, and assigning it to the "current" element will at least allow you to see an element other than the first one.

Also, from my ongoing tinkering, it appears that the _M_finish element is not (as I first thought) the last valid element in the vector. It appears to be more of a sentinel element...I'm getting the impression that vectors are sort of a cross between arrays and linked lists.

Hope this helps someone.

Perhaps put it on bugreports.qt.nokia.com

gdb --version

CONFIG += mobility

need this CONFIG in .pro file

Take a look at the "README":http://qt.gitorious.org/qt-creator/qt-creator/blobs/master/README provided for building Qt Creator from scratch. Most of the issues mentioned there apply to building Qt as well.

For Windows, we recommend using the slik svn command line client (see "http://www.sliksvn.com/en/download":http://www.sliksvn.com/en/download).

Thank you Koahnig and Tobias. I will look into those options as soon as possible. Thanks a lot

I know that it's not that simple because we have two files: header and cpp.
Actually it's very pleasant to work with QTCreator.

You should get the tup output in the compile output window. Do you see that?

The build issues will stay empty since creator does not know how to make sense of the output produced by tup.

How should I find out which headers need: extern "C"?
Thanks

[quote author="qtnext" date="1317988986"]I need to step inside Qt source code. I have installed Qt sdk, Qt source after using maintenance tools. The strange things is that there is no pdb files in QtSDk ? Do I need to manually compile Qt to be able to debug Qt Source code ? [/quote]

Is it possible to install the sdk for msvc? If you copuld not make this choice, than this is your problem.
You need to have the Qt libs compiled for the proper version of msvc, otherwise you will have problems.

Thanks, now I get ~400 errors when including fstream...so something is c. wrong. Anyone would have time to look into a project from osx to compile on linux? should be very simple but im stuck with errors alike above. thanks for sending me a pm.