I think #3 is a good option, but I would like to suggest using an interface similar to that used for state attributes. I.e. use an enumeration for the possible values instead of a bool, even if only two values are needed initially. Having a more uniform interface for handling inheritance in the scene graph will lessen the learning curve.
On Mar 18, 9:27 am, "Robert Osfield" <[EMAIL PROTECTED]> wrote: > The solutions I can think of right now are: > > 1) Change have the CullSetting::InhertacenMask default to 0x0 and > have all Viewer code to related Camera's and > SceneView to explicitly set the InheritanceMask to ALL_VARIABLES > > 2) Leave CullSetting::InheritanceMask as ALL_VARIABLE default, and > change all RTT/in scene graph Cameras to > explictly disable the InhertianceMask they do not need. > > 3) Leave CullSetting::InheritanceMask as ALL_VARIABLE default and > have the CullSettings::setVariable() calls all > optional disable the associated part of the InhertianceMask to > off. This disabling would be done by default. i.e > > CullSettings::setComputeNearFarMode(mode, bool > disableInhertianceOfComputeNearFarMode=true); > > I think option 3 would probably give us reasonable backwards > compatibility, but... it would hide a bit of what is going on w.r.t > InheritanceMask and be inconstistent with the way the rest of the OSG > works w.r.t set/get methods. > > Can anyone else think of any other options? > > Robert. > _______________________________________________ > osg-users mailing list > [EMAIL > PROTECTED]://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph... _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
