You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VertexArrayAttrib provides wrappers for VertexAttribFormat, VertexAttribIFormat, VertexAttribLFormat, but I couldn't find any wrapper for the following functions:
BindVertexBuffer
VertexAttribBinding
VertexBindingDivisor
It seems to me like it would be beneficial to abstract vertex buffer binding points by wrapping the index in a class (the same way a vertex array attribute is wrapped by VertexArrayAttrib), and implement the above three functions as members of this class.
I'd be willing to spearhead the implementation, but I'm not familiar with the template programming techniques used by oglplus, and I'm unsure of how to approach implementing a new class in a way that lines up with the rest of the library. Should I create an *Ops<> class, and if so, how should I use it? Are there any enumerations or existing classes that need to be updated?
VertexArrayAttrib
provides wrappers forVertexAttribFormat
,VertexAttribIFormat
,VertexAttribLFormat
, but I couldn't find any wrapper for the following functions:BindVertexBuffer
VertexAttribBinding
VertexBindingDivisor
It seems to me like it would be beneficial to abstract vertex buffer binding points by wrapping the index in a class (the same way a vertex array attribute is wrapped by
VertexArrayAttrib
), and implement the above three functions as members of this class.I'd be willing to spearhead the implementation, but I'm not familiar with the template programming techniques used by oglplus, and I'm unsure of how to approach implementing a new class in a way that lines up with the rest of the library. Should I create an
*Ops<>
class, and if so, how should I use it? Are there any enumerations or existing classes that need to be updated?Reference: https://www.khronos.org/registry/OpenGL/extensions/ARB/ARB_vertex_attrib_binding.txt
The text was updated successfully, but these errors were encountered: