General and Desktop

Glad I could help. Please prepend [SOLVED] to the thread title to let others know there's an answer here.

Items are rotated around their transform origin point, which by default is at (0,0) - upper left corner. You need to specify this origin to whatever you want - center of the image, bottom corner etc. with setTransformOriginPoint(x,y).

Apparently they will try to release the SDK in the 5.0.1 at the end of January ("official blog source":http://blog.qt.digia.com/blog/2012/12/19/qt-5-0/?utm_source=rss&utm_medium=rss&utm_campaign=qt-5-0)

You have a bug in your program. Probably dereferencing an invalid pointer or freeing memory twice. Debug your program with the standard debugger (stepping through code, placing break points, inspecting variable values, thinking very hard) or valgrind.

There is no Qt 4 SDK at this time, just stand-alone Qt 4 library packages. So you will need to install Qt Creator separately. The Qt 5 packages come with Qt Creator included and thus are basically a "Qt desktop SDK". There was an announcement claiming that the Qt 5 installer will be able to also install Qt 4 later (via an online installer). The old "Nokia Qt SDK" also has Qt 4, Qt Creator and support for the Nokia phone platforms, but that one is really dated by now.

@ m_palette.setColor(QPalette::All, QPalette::Window, m_color); m_palette.setColor(QPalette::All, QPalette::Base, m_color);@ That fixed it.

I have a problem in sharing a GLContext between two GLWidgets, I have Dual monitor system which has got NVidia Graphics Card, Monitors are configured as Screen 0 & Screen 1 ( Separate X Screens). and i am trying to create one GLwidget on Screen 0 and the second GLWidget on Screen 1, if Both GLWidgets are at same screen i am able to share the context but if i create a second GLWidget on Screen 1 context is not sharing. Advance Thanks for any help.

I think the problem is not with mdb file but with the driver. To open an Access database with a 64bit application you need a 64bit ODBC driver working properly. Odbcad is not the Access driver but an odbc dll only.

The first issue was because of the \n, it should be \n. The second issue was because of the \n, it should be \n and the \b, doesn't have to be there. (Though it has the same issue as the quotation, but only with keywords)

With dependency walker you have to make sure of two things: You use the same version as your app is ie. 32bit if your app is 32bit and 64bit if your app is 64bit, otherwise the misleading warning about different processor type appears. Make sure none of the Qt dlls are in the PATH or QT_DIR, otherwise it will pick them up and report no problem but your app won't start after deployment. The other thing is that dependency walker can't check for any dlls loaded dynamically, so make sure you deploy all the plugins you use, so platforms/qwindows.dll(most probably that's what you're missing), imageformats/qgif.dll or sqldrivers/qsqlite.dll and so on.

Is there any documentation that would help me do this manually ?

It works! Thank you Krysztorf Kawa!

You’re welcome. Feel free to prepend the title with ‘[Solved] …’ if your question has been solved to indicate that there is a solution inside.

How can you use main(int argc, char *argv[]) in a thread? The main function is the entry point of your app and what the "main" thread will execute first. If you create additional threads, they won't start from the "main" function!! Instead whatever API you use to create the thread will ask for a pointer to the thread "start" function. BUT: None of the thread API's I know (Win32, pthreads, QThread) has this signature for the "start" function: @int (*main)(int argc, char *argv[])@ Instead it's usually something like: @void* (*start)(void *param)@ So how do the values of argc and argv get into your thread's start function?

Simple - through the parent of both. Although not necessary - all you really need to connect two objects is pointers to their QObject base class.

I have solved the problem. It was rather silly mistake of mine. The line @LED(p1.x(), p1.y(), p2.x(), p2.y());@ creates a temporary object with correct x, y etc. values. But the object I added to scene remains uninitialized. Hence the junk values. The second issue is also simple to see. The boundingRect() function does not always include the red line, so it does not show.

I have noticed that there are some differences between source files in Qt versions. I'm using Qt 4.8.2 under Linux.

ChrisWQ67, http://qt-project.org/forums/viewthread/8595 , this link answered my questions. Thanks all.