Without low-effort, low quality trolls it might go back to being nearly as good as ?off

The WM_PAINT abstraction leak

The window gets a WM_PAINT. The code gets a device context, calls Draw(), then releases the context. It's an abtraction.

Draw() tries to read internal data and put it on screen. But the data has been swapped out. There is a two-second penalty as existing data is swapped out, and application data is read back from disk.

The user stares at a window with a hole in the middle. 95% of Windows apps are like this; and it feels so "broken".
Permalink Alex 
August 16th, 2005
I suppose that Windows could pre-paint the window with previously-painted data, before asking the application to repaint it.
Permalink Christopher Wells 
August 16th, 2005
Should have done it like BeOS did, and have a second thread just for the UI.
Permalink example 
August 16th, 2005
When you say the data has been "swapped out", do you mean virtual memory swap?
Permalink ronk! 
August 16th, 2005
Oops, you found an error!