On Saturday 09 July 2005 01:55, Marcus Lindblom wrote: > Dirk Reiners wrote: > >The highest MaterialGroup should probably have the highest priority. > >That's easy to fix, I just would like to hear if anybody has an > > argument against changing this behavior before I change it. > > Hmm.. Does this mean that it is will not be possible to define a > global state that is selectively overriden by chunks in > MaterialGroups further down in the graph? (or other materials which > do not use chunks).. Or what does this change imply more > specifically? > > It's quite easy to write a graphop/traversefunctor which > replaces/removes all materials in a subgraph. This is what I use to > modify the material of VRML-loaded graphs
I guess one can discuss endless about what is the right way to do things like this. IMHO having the possibility to override local material behaviour can be handy sometimes (defining clipping planes on a global state level). Maybe an additional field in the materialgroup if it is an override material (default: no) would allow more flexibility. And if one doesn't need it, not a big deal either, just don't use it. My 2 cents Matthias PS: This was a pro vote ;) ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
