Ability to reset internal state tracker about magnum HOT 5 CLOSED

two things i might add:

1. Although objects don't usually have id 0, it is still a valid binding value, for instance one can always call glBindVertexArray(0), which just "unbinds" any currently bound VAO.
2. Speaking of VAOs, it would be good to have some "stable" interface for the state object, that would allow user to set bindings he likes, right now VAO bind functions are part of Mesh class, as if the user is not supposed to have his own VAOs apart from the Mesh class

If you implement the reset function, consider to allow to specify which parts of the state tracker need to be reset.

from magnum.

1. Yes, 0 is valid binding value. I thought about using 0xFFFFFFFFu as disengaged binding value. As far as I know the drivers start with 1 for object IDs and not from the other end of the range.
2. What do you mean, exactly? The Mesh and MeshView classes should provide everything needed for drawing (when I implement all the missing multi/indirect/instanced/transform feedback functionality).

Partial state reset is a very good idea, thank you.

from magnum.

in 2: you have then to be somewhat sure in that you cover all possible use cases, even rare ones.

from magnum.

Yep, that's the plan (supporting everything what's possible with core GL, except maybe for client-side data).

from magnum.

Done (for all currently tracked state) in 4e50aee, more will come when state tracking is implemented for Renderer and other classes.

from magnum.