Re: PostMessage and unprocessed messages
"Giovanni Dicanio" <giovanni.dicanio@invalid.com> ha scritto nel messaggio
news:O5gnT1JgIHA.5900@TK2MSFTNGP02.phx.gbl...
"Joseph M. Newcomer" <newcomer@flounder.com> ha scritto nel messaggio
news:g213t3dk9jn8md6acg6mar8hhfsm3k4e9q@4ax.com...
// Wait thread termination
::WaitForSingleObject( m_workerThread->GetHandle(), INFINITE );
****
Wrong! This blocks the thread so it cannot process the pending messages,
so they still
leak.
No, because I have a PeekMessage loop after WFSO, so I scan for
WMU_WORKER_PROGRESS messages and delete the dynamically allocated data whose
pointer is in LPARAM.
Do NOT do a WFSO in this context.
As shown in another post, I did the PeekMessage loop to flush the
unprocessed messages after WFSO, and it seems working fine.
However, I must confess that this [WFSO] seems to me not the best
solution...
In fact using WFSO I'm blocking (even if for small time) the main GUI
thread, and I think this is not very good (for example, the GUI thread won't
process important messages like WM_PAINT, if my understanding is
correct...).
This solution seems to work fine in my particular test, because I think
there are few pending messages, but I think it won't scale up well.
I must try to implement Joe's solution based on updateControls and delay
closing.
Giovanni