Hi Paul,

On Thu, Jan 21, 2010 at 9:04 AM, Robert Osfield
<[email protected]> wrote:
> In terms of consistency the slave Camera's StateSet really should be
> passed on to SceneView so I'll have a think about how to implement
> this.

I've now added this functionality.  I introduced a SecondaryStateSet
into SceneView that sit in between the GlobalStateSet and the
LocalStateSet.  The master Camera's sets the GlobalStateSet, the slave
sets the SecondaryStateSet, and the LocalStateSet is kept for local
uniforms and other state settings that SceneView has traditionally
undertaken.

I've tested this by modifying the osgwindows example so that one
window has OpenGL lighting enabled and the other has it disabled at it
works fine.  I haven't checked in this test though...

An svn update will get these changes.  Now there is chance that user
code that has StateSet's attached to slaves that wasn't working so
they added an extra workaround might suddenly find their apps behave
differently - but my guess is that this will be a pretty small risk.
The new scheme is certainly more sensible.

Cheers,
Robert.
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to