Hi Marcus,
On Tue, 2005-07-12 at 09:55 +0200, Marcus Lindblom wrote:
>
> Understood. I just wanted to get my head around it. :) This would of
> course preclude the use of a 'default' material at the top node, but
> I suppose no-one uses that.
Not right now, no.
> Also, I was thinking a bit about possible
> future extensions, like merging State instances during draw, but that
> could perhaps be done by extending ChunkMaterial into a
> ChunkMergeMaterial which could implement a variety of combinating
> algorithms during render.
I want to do that for the next version, I just need to find a way to
make it efficient.
> I use a static version of this currently,
> manually adding missing chunks from some material to other materials in
> the graph (i.e. when applying shaders to VRML-objects, and similar.=
Yup, that works, too.
> Sure. Sorry for causing some ruckus. I just got a bit worried about to
> the long-term effects (w.r.t. future developments of OpenSG) by this change.
No problem, concerns are always welcome. We always want to make things
better, but without knowing what people do and how they're using the
system we can't know if a change would be problematic for some of you.
BTW, I checked in the change and a test program.
Yours
Dirk
-------------------------------------------------------
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
