Khronos Public Bugzilla
Bug 908 - EXT_direct_state_access: no selector-free way to change VAO's texture coordinate set enable
EXT_direct_state_access: no selector-free way to change VAO's texture coordin...
Status: NEW
Product: OpenGL
Classification: Unclassified
Component: Registry
unspecified
PC Windows
: P3 normal
: ---
Assigned To: Jon Leech
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-17 15:23 PDT by Mark Kilgard
Modified: 2013-07-17 15:58 PDT (History)
0 users

See Also:


Attachments
updated EXT_direct_state_access spec, see Issue 32 (209.18 KB, text/plain)
2013-07-17 15:23 PDT, Mark Kilgard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Kilgard 2013-07-17 15:23:44 PDT
Created attachment 157 [details]
updated EXT_direct_state_access spec, see Issue 32

Developers reported EXT_direct_state_access lacked a selector-free to update (and query) a particular texture coordinate set's enable in a VAO.  This was simply an oversight.  The updated specification adds NEW language saying glEnableVertexArrayEXT and glDisableVertexArrayEXT can accept GL_TEXTUREi names.  NVIDIA drivers didn't have this functionality but we are working to add it.

I'm attaching an updated EXT_direct_state_access specification that corrects this oversight.  See the NEW issue 32 for more discussion of the issues and its resolution.

There is no new API functions or procedures added.  Instead, tokens are documented as working now.
Comment 1 Jon Leech 2013-07-17 15:58:30 PDT
(In reply to comment #0)
> Created attachment 157 [details]
> updated EXT_direct_state_access spec, see Issue 32
> 
> Developers reported EXT_direct_state_access lacked a selector-free to update
> (and query) a particular texture coordinate set's enable in a VAO.  This was
> simply an oversight.  The updated specification adds NEW language saying
> glEnableVertexArrayEXT and glDisableVertexArrayEXT can accept GL_TEXTUREi
> names.  NVIDIA drivers didn't have this functionality but we are working to
> add it.

Are you running these changes by other vendors who implement the EXT? I ask
since I've very recently heard complaints from other vendors that NVIDIA was
unilaterally changing the EXT and creating behavior differences with their
implementations which developers had complained about. Someone suggested
that perhaps there should instead be EXT_dsa2 (dsa3, etc.) for such changes.