http://bugs.winehq.org/show_bug.cgi?id=2398
------- Additional Comments From jotdot@shaw.ca 2006-06-03 22:01 ------- I'm sure Windows uses a separate window for the opengl context. I've seen it in action before. I do some graphics programming in Windows and the normal method to handle window messages in the graphics loop is (psuedo code): while no quit message received .. while more windows messages .... process next windows message .. process one frame of graphics When I inadvertently messed up my code to: .. Process one window message (if any) .. process one frame of graphics I noticed that the gl window lagged behind everything. It was apparent when moving and resizing that the opengl window was a separate window by itself. This was the result of messages queueing up (my frame took a fair amount of time) and thus responses were not instant. It appeared as the opengl window trailing behind the client area as if it was "floating" and not tracking the move/resize as fast as it should.