-
- Downloads
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.
Showing
- dlls/wined3d/buffer.c 3 additions, 0 deletionsdlls/wined3d/buffer.c
- dlls/wined3d/context.c 7 additions, 47 deletionsdlls/wined3d/context.c
- dlls/wined3d/cubetexture.c 4 additions, 0 deletionsdlls/wined3d/cubetexture.c
- dlls/wined3d/device.c 7 additions, 1 deletiondlls/wined3d/device.c
- dlls/wined3d/directx.c 3 additions, 0 deletionsdlls/wined3d/directx.c
- dlls/wined3d/shader.c 3 additions, 0 deletionsdlls/wined3d/shader.c
- dlls/wined3d/surface.c 3 additions, 0 deletionsdlls/wined3d/surface.c
- dlls/wined3d/swapchain.c 3 additions, 1 deletiondlls/wined3d/swapchain.c
- dlls/wined3d/swapchain_base.c 3 additions, 1 deletiondlls/wined3d/swapchain_base.c
- dlls/wined3d/texture.c 4 additions, 0 deletionsdlls/wined3d/texture.c
- dlls/wined3d/volume.c 3 additions, 0 deletionsdlls/wined3d/volume.c
- dlls/wined3d/volumetexture.c 3 additions, 0 deletionsdlls/wined3d/volumetexture.c
- dlls/wined3d/wined3d_main.c 1 addition, 0 deletionsdlls/wined3d/wined3d_main.c
Loading
Please register or sign in to comment