Hi Johannes, A Uniform is not meant to change it's name or type through the life of an application as the shaders that they are associated with will also normally be invariant through the lifetime of the application.
If you want a Uniform to have a different name or type it's essentially now a different Uniform and has a different mapping the shaders it is associated with. For changing Uniform name or type mid way through an application means that the Shader's it's assoicated with are also changing which really doesn't suggest that the we are talking about different Uniforms and Shaders but in your case you don't want to both creating new ones that map this logic, instead want to reuse. Creating new Uniform and Shaders when you have new uniforms and shaders seems logical to me. Robert. On 3 December 2013 10:07, Johannes Scholz <[email protected]> wrote: > Hi, > > in our application we just created an user interface for setting up > osg::Uniform data on our nodes for 'artist usage' (setting shader input > values like colors or textures). > > Now I encountered that the uniform name must not be changed which is from > a artist user perspective quite inconvenient. > > As I expect this to be intended for some reason I will make a workaround > copying the uniform adding it with a new name. > > But could somebody explain me what was the reason for the decision making > the uniform name not changeable? > > Thank you! > > Cheers, > Johannes > > ------------------ > Read this topic online here: > http://forum.openscenegraph.org/viewtopic.php?p=57529#57529 > > > > > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
