Care to elaborate how you got around this? I tired several different things and couldn't get it done.
Care to elaborate how you got around this? I tired several different things and couldn't get it done.
So the situation is analogous to the DOM in web browsers. The calls are synchronous and run in the main thread. As the web has taught us though, single-threads and blocking graphics calls can go a long way :)
Just wondering how you got around this...I see you're using processEvents in QApplication.
from http://doc.qt.nokia.com/4.7-snapshot/thread-basics.html:
GUI Thread and Worker Thread As mentioned, each program has one thread when it is started. This thread is called the "main thread" (also known as the "GUI thread" in Qt applications). The Qt GUI must run in this thread. All widgets and several related classes, for example QPixmap, don't work in secondary threads. A secondary thread is commonly referred to as a "worker thread" because it is used to offload processing work from the main thread.
That's right. AFAIK everything is running in a single thread.