Hi Farshid, Luca,
You are absolutely right! I had mistakenly assumed that the description
list was supported by all osg::Object derived classes. Well, that puts a
big dent in our plans :(
Argh, I had made the same assumption.
Does anybody know if the new meta-data system will support all
osg::Object derived classes?
I think so, since it will essentially supersede the UserData. I think
that's why we made the wrong assumption above.
One option would be to put the description string in the name of the
stateset object. Another option would be to use the user data field, but
that would require a custom serializer.
In the name, that would make a really long name!
In the UserData might be a good idea if we can think of a way to make it
readable for anyone. I guess it would also limit us to using the "new"
formats (osgt, osgb, osgx) and not the "old" ones (osg, ive).
Let me know if you have another idea.
Nope, not for now... I'll keep thinking about it though.
J-S
--
______________________________________________________
Jean-Sebastien Guay jean-sebastien.g...@cm-labs.com
http://www.cm-labs.com/
http://whitestar02.dyndns-web.com/
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
