General and Desktop

Problem solved but just to clarify the "Module with different CPU were found” output the DW gives - it's a long story but the short version is that this happens when you check your win32 app with x64 version of DW or x64 app with win32 DW or have e.g win32 Qt libs in PATH and use x64 DW. Just keep them all in line to avoid it. The IEShims.dll is a bogus warning, no neeed to include it with your app.

Hmmm, my version also does that unless I resize the content widget enough to get the title on the title bar, then I can move it. No obvious solution springs to mind. You could perhaps play with the window flags to remove the system menu etc.

Hey fellas, Sorry i forgot to post my result here: The following solved the problem (like broadpeak said! Thank you!) In the .pro file just add the line @CONFIG += rtti@ That's it. See u guys around

No problem! Be sure and edit your first post and add [Solved] to the title. Thanks!

Indeed, it does not do the trick completely... After deep testing we found that when targeting Qt application built against Qt framework under 4.7 it does not work. Does anyone know why CGEventKeyboardSetUnicodeStringis not taken into account by Qt event monitoring loop ?

Ok I got my error. I have to write @QCOMPARE(db.open(), true)@ But I still am looking forward to any suggestions that may help me to test the methoes of other subprojects in my test projects.

"Here":https://docs.google.com/open?id=0B2SoBuawTfgOQk04SEg3bGEzY0E's what I want to do. What is the best way to transfer the widgets parenthood between the pages? A solution could be to subclass the QWidget that represents the page and make the page reparent all shared widgets in the show event. Or another solution could be to keep track of when the QWidget's parent gets changed: @ class QWidget { ... protected: ... virtual void changeEvent(QEvent* event) { if (event->type() == QEvent::ParentChange) or if (event->type() == QEvent::ParentAboutToChange) } ... }; @ Probably the best solution is to rework the whole page's layout everytime.

Can you check the executable using the Dependency Walker? Maybe can show you something... I'm not sure but I don't think that can be the Video Graphics or GPU Driver... Did you check a CPU usage when you start the qt application?!

Set a breakpoint in QGraphicsItem::update() and see where it's coming from.

Really great! Thank you for your answer

The about dialog of Qt Creator will report the Qt version used by Qt Creator. That is a different Qt version than the one used by your applications. You do not want to have your IDE stop working when you mess around with your Qt versions to make them work best for your applications, do you?

If you think this is a bug, then please "file a bug report":http://bugreports.qt-project.org/ . It must have taken a lot of time to get all this researched and written down, it would be a waste for this to not get the attention of the responsible developer. In the bugtracker such attention is guaranteed, here it is unfortunately not.

The development branch for 5.1 should open up for commits very soon now. :)

What happens is that Layouts don´t work good with OpenGL underneath. It appears black, doesn´t repaint openGL. If you remove the layout, it works, but then you have to position widgets around by hand. And if you have stylesheet assigned and round corners, the corners will be black too. A work around is to add this flag: @ widget->setAttribute( Qt::WA_TranslucentBackground ); @