Norman Vine wrote:
Hmm, I was just thinking we have something to start with:David Megginson writes:Martin Spott writes:
> > As far as I know, no one has started documenting the propperly, mainly > > because they tend to change rather quickly.
> > You probably hit the nail ;-)
Aside from that, there will probably be a major restructuring when we
add multi-vehicle support.
Neither of which is a reason *not* to start a master list at least of new and changed items Seriously how much more work would it be to add/change an entry to the master list at the same time as the code was submitted into the CVS IMHO this should be a requirement for any change in the property tree and would help a lot As a wise man once said The long journey starts with the first step
You can save the current state of the properties using the File menu. The output will be an XML file containing all the properties available in the curent session!
Erik
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
