Hi! I've been noticing this strange behavior and I really can't understand what could it be related to.
I have a worker thread which loads some images in a loop and sends a signal in each iteration. This signal is connected to a slot in the GUI thread which simply shows these images in a QGraphicsView.
This structure has always been working very good, but now I tried it on another system (both are Windows CE), and it seems its not working properly. When I start the application, the images coming from the thread are simply not rendered in the QGraphicsView. They are loaded correctly in the background, but not rendered. After I click anywhere, those which are already loaded appears suddenly, and the others begin to appear correctly as soon as those are loaded.
After this process has finished, everything is OK. I can even start this thread again, and the images are correctly shown as expected, as soon as they are loaded. The problem is only immediately after the application is loaded.
Any idea why this could be happening. As I've recently been taught, I thought it could be a problem of events not processed, but I tried placing QApplication:rocessEvents() after the update method without any success...
Any other idea?
Thanks for any advice!




rocessEvents() after the update method without any success...
Reply With Quote
Bookmarks