Hi Sebastian,
On 9 September 2013 17:27, Sebastian Messerschmidt < [email protected]> wrote: > Looking into it I guess that would be only half a solution. Basically I > don't feel very comfortably with the UserData approach here at all. > I'd rather move it to vertex attributes, as FID, SMC etc. are properties > of triangles rather than geodes... > Given that type of granularity then attaching the UserData to the osg::Array or osg::PrimitiveSet would appropriate. > In general I tend to agree, I'll think of some configurable helper class, > setting up the UserData as configured by the user. > Maybe you can give some advises here, how to make it clean and > maintainable. > I'm that familiar with OpenFlight format/Creator, nor the author of the OpenFlight plugins so I'm a bit of dis-advantage to recommending the most appropriate way forward. If one doesn't go the UserData approach then perhaps one could have a callback attached to an osgDB::Option object and have this callback take the OpenFlight properties of interest and the osg::Object that are associated with it and let the callback decide how to post process the data. osgSim already have classes like the DOF transform to support OpenFlight so perhaps adding a callback tailored to the requirement of OpenFlight isn't too much of a stretch. Robert.
_______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
