Re: [GD-Windows] message pump problem
Brought to you by:
vexxed72
From: Marin K. <m.k...@in...> - 2003-12-02 17:25:18
|
> Here's a little trivia plus a trick: > In addition to what Jon said, the explanation for this behavior is that, > unlike nearly all other messages, WM_PAINT is not queued up. Rather the > way it works is that, when GetMessage & PeekMessage detect that all > queued messages have been handled, they go through the list of windows > associated with the thread and if one is found with an invalidated > region, they return a synthesized WM_PAINT message for it. This way > there's no problem with paint messages stacking up and painting doesn't > get in the way of higher priority things. EndPaint validates the window > and that's why you're supposed to call it. > Make sense? Yeah, it makes perfect sense now that I've accustomed to the idea. It was all jibberish while I was reading about it in the MSDN. :-) -- Marin Kovacic Lemonade Productions http://www.lemonade-p.com |