Hi Alberto,
Alberto Luaces wrote:
El Martes 27 Mayo 2008ES 16:58:21 Paul Melis escribió:
dirtyDisplayList();
dirtyBound();
When using direct access to the list you will have to call these
yourself...
Well, I think osg users are used to call these functions themselves pretty
often when dealing with dynamic geometries, but it's just a matter of
style :)
No offense, but I consider using the underlying data structure like in
this particular case bad style, it's asking for trouble.
The problem is that directly adding to/removing from the underlying
vector doesn't include all the semantics of adding/removing of the
higher level API. So whenever the higher level add/remove is altered to
say, include more operations, you might not become aware of this until
you code that directly accesses the vector starts misbehaving. Removing
the public access to the primitive set list would help to avoid this,
but it seems other OSG classes need access to it, e.g. osgUtil::Optimizer.
Regards,
Paul
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org