GL_APPLE_FENCE shares the same token in dlls/wined3d_gl.h with GL_FENCE_STATUS_NV.

[ace102]

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_g...
Sent from the Wine - Devel mailing list archive at Nabble.com.

[Henri Verbeet]

2009/4/27 ace102 <mgavl69(a)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.

[Ben Klein]

2009/4/28 ace102 <mgavl69(a)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_g...
> Sent from the Wine - Devel mailing list archive at Nabble.com.

Is it just me or did this message get sent three times? :P

[John Klehm]

> Is it just me or did this message get sent three times? :P

3 times for me too.