"Jon S. Berndt" wrote:
> > John, actually, what you're looking for is a routine that allows you to
> > dump the whole property tree at runtime into a file and allow
> > re-loading this as a preset. In order not to break current behaviour it
> > would be necessary to compile a 'standard-preset' file that would be
> > loaded upon reset unless otherwise defined.
> >
> > Correct ?
> I wonder, however, if there are some important terms that are not
> properties. Internal states may need to be saved, but are not stored as
> proeprties, therefore an approach such as you suggest may not work.
Certainly such a procedure that 'replays' the property tree does not
affect _every_ state that may be involved. Still I'm convinced that it
comes pretty close: You're in air, velocity is as expected and you
don't have to toggle any switches or move any handles. I guess it
serves much better for what John would like to see than the current
approach,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
