Jim Wilson writes:
> That's what I meant. Thanks for the example. BTW what would be
> the application of property tree swapping, as opposed to say the
> method that the view manager uses?
Curt and I have discussed this before (either online or offline). We
could certainly have per-vehicle subtrees, i.e.
<vehicle n="0">
<position>
...
</position>
<orientation>
...
</orientation>
<controls>
...
</controls>
...
</vehicle>
and so on, and that would let us share some common, sim-wide
information at the top level, and would make all program-wide
information available at a single glance. The alternative is to use
the multi-process model rather than a multi-thread model, and to swap
entire property trees in and out like memory pages; we'll certainly
avoid a lot of bugs that way (because the wrong properties simply
won't be available).
What does everyone else think?
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
