wined3d: Explicitly document some more consequences of GL locking policy.
authorHenri Verbeet <hverbeet@codeweavers.com>
Thu, 2 Sep 2010 17:25:00 +0000 (19:25 +0200)
committerAlexandre Julliard <julliard@winehq.org>
Fri, 3 Sep 2010 09:05:10 +0000 (11:05 +0200)
commitbc2db78c3a659986d2f5e2b8e503ab5267cdf29c
tree2c38fc478040663d8276f6acbb3a3d3bb37914e8
parentc6a655622cb5b5f32bb32fc207ded39b09acda99
wined3d: Explicitly document some more consequences of GL locking policy.

The basic rule is that you can't call anything that takes the user32 / gdi32
lock while under the GL (winex11) lock. As a consequence, you can't call
anything like context_acquire() or context_destroy() either.
13 files changed:
dlls/wined3d/buffer.c
dlls/wined3d/context.c
dlls/wined3d/cubetexture.c
dlls/wined3d/device.c
dlls/wined3d/directx.c
dlls/wined3d/shader.c
dlls/wined3d/surface.c
dlls/wined3d/swapchain.c
dlls/wined3d/swapchain_base.c
dlls/wined3d/texture.c
dlls/wined3d/volume.c
dlls/wined3d/volumetexture.c
dlls/wined3d/wined3d_main.c