Quote Originally Posted by wysota View Post
You can't put your own custom events "on hold" if processEvents() doesn't support that. You can only discard an event by filtering it out.
That's a pity

If there is somebody from the developer team is watching this thread ...

Wouldn't it be nice to have a new ProcessEventsFlag ExcludeUserDefinedEvents, which suppresses external influences in a way like ExcludeUserInputEvents and ExcludeSocketNotifiers do?

This supports a more strict separation of GUI related and process/application related parts even in an event driven design.