opengl32: make the old code before the "sync the dibsection to its pixmap" patch be selectable at runtime

Raphael fenix at
Tue Mar 21 02:33:17 CST 2006

Hi Stefan,

On Tuesday 21 March 2006 01:41, Stefan Dösinger wrote:
> Am Montag, 20. März 2006 23:26 schrieb Lionel Ulmer:
> > Well, in OpenGL each thread can have its own context (and you can also
> > bind a context to only one thread which explains why multi-threaded D3D
> > applications are such a pain to support). So you can have multi-threaded
> > GL applications with each thread having its own GL context.
> What says that a gl context can be used by one thread only? In the
> glxDestroyContext man page it sounds like a context has a sort of reference
> count, and it can be used by multiple threads.

You're right you can use the same context for many threads.
you only have to "map" it to each threads (using MakeCurrent APIs)
Anyway i have seen many problems when using the same context active for too 
many threads (seems the nvidia drivers don't like this kind of behavior)

> A little bit OT, but related to multi-threaded opengl is a bug in the dri
> radeon driver( I've
> reported it to the dri devs but didn't get any response so far.


> Stefan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url :

More information about the wine-devel mailing list