Hi,
The OpenSceneGraph 3.0 Beginner's Guide states that "OSG doesn't
support algorithmic topology functionalities at present, probably
because it seems a little weird for a rendering API to implement
this."
I'm fine with this.
Now, I've written a ReaderWriter plugin to read a custom file format
that encompasses such topological informations, e.g. triangle/quad
indices of the geometry defining regions on the model.
Is osg::Object::set/getUserData adequate to serialize such topological
informations in order to later display them (e.g. displaying regions
of the model with different colors) or am I better developping my own
interface?
I've seen the osgUtil::EdgeCollector in OSG documentation, but it
seems to do the reverse, i.e. extract topological informations of a
geometry (edges, vertices, triangles) whereas I know them beforehand.
And this won't tell what's the best practice to later store the
results of osgUtil::EdgeCollector.
Thanks,
Émeric
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
