Frederic BOUVIER writes:
> But I don't think there is a huge penalty here. Classes that are doing
> tying now must store the SGPropertyNode as a separated pointer for tying
> and untying.
They don't, actually -- the property manager takes care of storing the
node. You just do something like
fgTie("/foo/bar", this, &Foo:getBar, &Foo:setBar);
at the start, and
fgUntie("/foo/bar");
and the end, and for the rest of the time you can pretend the property
system doesn't exist.
All the best,
David
--
David Megginson, [EMAIL PROTECTED], http://www.megginson.com/
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
