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

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

--- Comment #13 from Dmitry Timoshkov  2013-03-19 08:44:57 CDT ---
(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.
> and message loop based on PeekMessage without
> WaitMessage will consume all CPU cycles it can get. See also bug 30736, which
> is caused exactly by this.

It doesn't mean that in Windows it behaves like this.