Hi list, my use-case is this: I have data structures that cannot be rendered directly but can be transformed to something that is renderable. All algorithms manipulating data work on my own data structures. After the algorithms are done, I would like to update the geometry to reflect the changed data.
I'm unsure if I should extend a osg::Geode, add my datastructure as a member and a rebuild() member funtion or if it makes more sense to extend a osg::Drawable and go from there. Basically, the setUserData() function already does what I want but it lacks a way to issue an update. Alternatively, I can just store my data separately and use setUserData to have to keep pointers to the associated data and work from there. Cheers, Philipp _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
