On Sat, 4 Apr 2009, Tim Moore wrote:
> 1) Write the full vector every time a component is changed. This means
> potentially 4 times the memory traffic to change a color, and leaves the
> values stored in OSG in an inconsistent state for a time.
>
If efficiency is of the outermost concern you could tie each of the
components of a double vec[4] to properties, e.g.
color/{red,green,blue,alpha}. That would make it possible for the internal
C++ code to use the vector representation while still preserving a nicely
structured and typed property tree for external access.
> If people really don't like the effects syntax, I might be willing to
> hold my nose and use the existing property implementation. I'm also not
> committed to having the effects properties be of class SGPropertyNode;
> they might be a subtype.
If you really must have it, please put it in a subtype.
Cheers,
Anders
--
---------------------------------------------------------------------------
Anders Gidenstam
WWW: http://www.gidenstam.org/FlightGear/
------------------------------------------------------------------------------
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
