[Bug 33235] Tab control doesn't notify new parent set with SetParent()

http://bugs.winehq.org/show_bug.cgi?id=33235

--- Comment #14 from Daniel Jelinski  2013-03-19 09:56:10 CDT ---
(In reply to comment #13)
> (In reply to comment #12)
> > > If you mean that PeekMessage doesn't yield cpu and therefore it shouldn't be
> > > used to write message loops, then this is not correct. Message loops that use
> > > PeekMessage are equivalent in behaviour to the ones that use GetMessage.
> >
> > PeekMessage returns immediately,
>
> No, it doesn't.

Interesting. Are you saying that the following loops are equivalent?
while (GetMessage(&msg, NULL, 0, 0))
{
    DispatchMessage(&msg);
}

while (1)
{
    PeekMessage(&msg, NULL, 0, 0, PM_REMOVE);
    if(msg.message == WM_QUIT) break;
    DispatchMessage(&msg);
}