[osg-users] BAD design of TextureAttribute

[Julien Valentin]

Hi,
Searching for the bug once again i found that there were changes in Texture base class....I will dig what was the purpose of this new design but i suspect its use is to conform with the pragma pipeline.
At first glance, making tu member of TextureAttribute is really a bad design but perhaps there a reason...
What's sure is that is no reliable to be use outside of the pipeline conformance path: so 
getMember {return _activetu} should really be removed!!

Further, I can't see a usecase whare TextureAttributes in the same ss share a common texture unit :~  so member of textures should stay 0


Thank you!

Cheers,
Julien

------------------
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=73208#73208