[Interest] PeekMessage, DispatchMessage and Qt events dispatching

[Prav]

Hi, Thiago.

>> So here is my question is there a bug in Qt or does DispatchMessage
>> shouldn't be called ?
> Moreover the execution stack is never unstacked i.e DispatchMessage doesn't return.

> Don't call it. Qt integrates with the Windows event loop, so this behaviour is
> expected. Ditto for Cocoa event loops and for glib: if you cause them to
> dispatch, Qt event processing will be woken up and deliver pending events.
It seems expected that next Receiver::work() processing started but how is that DispatchMessage NEVER returns?