- 19 Mar, 2010 5 commits
-
-
Damjan Jovanovic authored
-
André Hentschel authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
- 18 Mar, 2010 35 commits
-
-
Alexandre Julliard authored
-
Nikolay Sivov authored
-
Aric Stewart authored
-
Aric Stewart authored
-
Damjan Jovanovic authored
-
Damjan Jovanovic authored
-
Julian Rüger authored
-
Maarten Lankhorst authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Jacek Caban authored
-
Jacek Caban authored
-
Jacek Caban authored
-
Jacek Caban authored
-
Jacek Caban authored
-
Jacek Caban authored
-
Jacek Caban authored
-
Nikolay Sivov authored
-
Nikolay Sivov authored
-
Nikolay Sivov authored
-
Piotr Caban authored
-
Piotr Caban authored
-
Piotr Caban authored
-
Piotr Caban authored
-
Piotr Caban authored
-
Henri Verbeet authored
Unfortunately there are plenty of other places left. Perhaps we should consider creating our own window when the context becomes invalid and making the context current on that instead.
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
Updating a texture while it is attached to the currently bound FBO is something GL implementations tend to get wrong. NVIDIA fails at glTexSubImage2D(), fglrx and Mesa with glTexImage2D(). I'm afraid to try what happens on OS X. Fortunately we never use glTexImage2D() while a texture is attached to an FBO, so we only need to care about glTexSubImage2D().
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
What happens is that we get the WM_WINE_SETACTIVEWINDOW message sent by the other thread after we already changed the foreground window back to our own window.
-