Re: GL_APPLE_FENCE shares the same token in dlls/wined3d_gl.h with GL_FENCE_STATUS_NV.
2009/4/28 ace102 mgav...@juno.com: Hi, I noticed GL_APPLE_FENCE shares the same token in dlls/wined3d_gl.h with GL_FENCE_STATUS_NV. GL_FENCE_STATUS_NV http://www.opengl.org/registry/specs/NV/fence.txt Currently 0x84F3 GL_APPLE_FENCE http://www.opengl.org/registry/specs/APPLE/fence.txt Currently 0x84F3 Should be 0x8A0B from documentation. Is this by design or just something that slipped through the cracks? Thought I should alert someone just in case.:) Thanks. - Error:Success -- View this message in context: http://www.nabble.com/GL_APPLE_FENCE-shares-the-same-token-in-dlls-wined3d_gl.h-with-GL_FENCE_STATUS_NV.-tp23261485p23261485.html Sent from the Wine - Devel mailing list archive at Nabble.com. Is it just me or did this message get sent three times? :P
Re: GL_APPLE_FENCE shares the same token in dlls/wined3d_gl.h with GL_FENCE_STATUS_NV.
Is it just me or did this message get sent three times? :P 3 times for me too.
GL_APPLE_FENCE shares the same token in dlls/wined3d_gl.h with GL_FENCE_STATUS_NV.
Hi, I noticed GL_APPLE_FENCE shares the same token in dlls/wined3d_gl.h with GL_FENCE_STATUS_NV. GL_FENCE_STATUS_NV http://www.opengl.org/registry/specs/NV/fence.txt Currently 0x84F3 GL_APPLE_FENCE http://www.opengl.org/registry/specs/APPLE/fence.txt Currently 0x84F3 Should be 0x8A0B from documentation. Is this by design or just something that slipped through the cracks? Thought I should alert someone just in case.:) Thanks. - Error:Success -- View this message in context: http://www.nabble.com/GL_APPLE_FENCE-shares-the-same-token-in-dlls-wined3d_gl.h-with-GL_FENCE_STATUS_NV.-tp23261485p23261485.html Sent from the Wine - Devel mailing list archive at Nabble.com.
Re: GL_APPLE_FENCE shares the same token in dlls/wined3d_gl.h with GL_FENCE_STATUS_NV.
2009/4/27 ace102 mgav...@juno.com: Is this by design or just something that slipped through the cracks? Thought I should alert someone just in case.:) That's broken, but fortunately we don't use it. I'll write a patch, thanks for mentioning this.
