We've got some problems with widget repainting and user defined events generated by the underlaying process.
That's the situation:
- Some event handling causes to change the appereance of a dialog (includeing call to update()). This will get visible during a subsequent event processing of the corresponding painting event.
- Some thread of the underlaying process is posting application specific events (of type QEvent::User) to the GUI thread. This forces the main thread to start a more or less expensive handling.
Unfortunately, the application events may delay the re-painting if they are posted just before the update() call.
To re-draw that widget as soon as possible I'm calling processEvents() during the event handler routine. But, how can I suppress the delivery of the application events along with the user input events (as defined by QEventLoop::ExcludeUserInputEvents) when calling processEvents()
Bookmarks