[osg-users] osg::StateAttribute::PROTECTED meanings

2010-01-20 Thread Trajce Nikolov
is this meaning the attribute can not be overwritten from the top of the hierarchy? is so, does not work for me Nick http://www.linkedin.com/in/tnick Sent from Izmit, 41, Turkey ___ osg-users mailing list osg-users@lists.openscenegraph.org

Re: [osg-users] osg::StateAttribute::PROTECTED meanings

2010-01-20 Thread Thrall, Bryan
Trajce Nikolov wrote on 2010-01-20: is this meaning the attribute can not be overwritten from the top of the hierarchy? is so, does not work for me Yes, that is the meaning. However, the top of the hierarchy can use OVERRIDE to override the PROTECTED state, IIRC. Can you give an example

Re: [osg-users] osg::StateAttribute::PROTECTED meanings

2010-01-20 Thread Trajce Nikolov
well, I fixed it with a shader. But, if this is meant to be protected, then it shouldnt be overriden I think Nick http://www.linkedin.com/in/tnick Sent from Izmit, 41, Turkey On Wed, Jan 20, 2010 at 4:50 PM, Thrall, Bryan bryan.thr...@flightsafety.com wrote: Trajce Nikolov wrote on

Re: [osg-users] osg::StateAttribute::PROTECTED meanings

2010-01-20 Thread Paul Martz
Thrall, Bryan wrote: Yes, that is the meaning. However, the top of the hierarchy can use OVERRIDE to override the PROTECTED state, IIRC. Actually, PROTECTED keeps the state from being overridden. The default inheritance is INHERIT, which means that state inherits down the scene graph unless

Re: [osg-users] osg::StateAttribute::PROTECTED meanings

2010-01-20 Thread Jason Daly
Paul Martz wrote: On a tangent... These really seem like misnomers. INHERIT really _doesn't_ inherit when the child sets the same state, and OVERRIDE actually forces inheritance to happen. So if I were going to rename them, I'd have something like this: old namenew name INHERIT

Re: [osg-users] osg::StateAttribute::PROTECTED meanings

2010-01-20 Thread Trajce Nikolov
here was my case. and also this might have something to do with lazy state update the top node has 3 textures assigned the children only one with setting 0 and protected I was expecting the child to have only one texture, but it inherits the additional textures from the top node as well. So I

Re: [osg-users] osg::StateAttribute::PROTECTED meanings

2010-01-20 Thread Jason Daly
Trajce Nikolov wrote: here was my case. and also this might have something to do with lazy state update the top node has 3 textures assigned the children only one with setting 0 and protected I was expecting the child to have only one texture, but it inherits the additional textures from

Re: [osg-users] osg::StateAttribute::PROTECTED meanings

2010-01-20 Thread Trajce Nikolov
Hi Jason, that is what I exactly did. I put the PROTECTED there becaouse the parent has OVERRIDE set on it. Did not worked :-) ... Nick http://www.linkedin.com/in/tnick Sent from Izmit, 41, Turkey On Wed, Jan 20, 2010 at 6:23 PM, Jason Daly jd...@ist.ucf.edu wrote: Trajce Nikolov wrote: