> The problem is that managing runtime customizable multi-pass, 
> multi-stage rendering is not straight forward, and 
> unfortunately this complexity has spilled over into the API 
> to control it.  I haven't yet found a neat way of making it 
> more straight forward without loosing the power that it 
> provides.  One day I will, but it'll take a period of quiet 
> contemplation, but alas its been about 6 years since I had that...

Do you recall enough of the current implementation to at least enumerate the
features and functionality you intended to expose? If so, maybe someone else
could redesign the API. Right now I don't have much to go on because, other
than render order and sort order, and the features Paul listed, I'm not sure
what capabilities are supposed to be exposed by bin number and bin name.
   -Paul

_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/

Reply via email to