Excuse me if I let you think I insist but: When I first wanted to integrate subroutine in osg, I had to hack both StateSet and State as well as GLObjectVisitor... I may be lazy but I had prefered to use a StateAttribute rather than get readability of other files getting worse Isn't a comment in StateAttribute'sTypes to prevent ones to put Program after SubRoutineUniform would be preferable to all this osg hacking?
robertosfield wrote: > On 20 June 2016 at 13:47, Julien Valentin <> wrote: > > > I don't understand why you would reorder StateAttribute Types..? > > > > The problem is that there is the possibility that they could be > re-ordered, if you forgot that this issue existed made the change to > clean up order to make things more logical for some future version of > the GL/OSG you wouldn't see the problem first hand until some niche > users user the feature in a particular way. The problems that would > manifest would be subtle and hard to diagnose. > > Sure it's hypothetical but problems like this do occur for time to > time, the best way is never write in this problems to start with. > _______________________________________________ > osg-submissions mailing list > > http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org > > ------------------ > Post generated by Mail2Forum ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=67696#67696 _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
