(Please ignore this second question. I see that setAttributeAndModes()' second param is actually a mode value (on/off) for the attribute's associated mode (if it has one). And I see that setAttribute() is the method that takes an override value as a second param.) But I'm still curious about the code comment block that was in my original post on this thread. -Paul
_____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Martz Sent: Friday, February 09, 2007 2:15 PM To: 'osg users' Subject: RE: [osg-users] StateAttribute comment clarification And then as a follow-up question... I'm curious about the name of the entry point StateSet::setAttributeAndModes(), as it seems that a more appropriate name would be setAttributeAndOverrideValue(). (Funny how I never think about this stuff until I try to document it.) -Paul _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Martz Sent: Friday, February 09, 2007 2:13 PM To: 'osg users' Subject: [osg-users] StateAttribute comment clarification I'm curious about the following comment block in StateAttribute: /** list values which can be used to set either GLModeValues or OverrideValues. * When using in conjunction with GLModeValues, all Values have meaning. * When using in conjection with StateAttribute OverrideValue only * OFF,OVERRIDE and INHERIT are meaningful. Isn't it the case that OFF is meaningless for an attribute, but PROTECTED does have meaning? Paul Martz Skew Matrix Software LLC http://www.skew-matrix.com <http://www.skew-matrix.com/> 303 859 9466
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
