On 2 Nov 2010, at 14:14, Martin Spott wrote: > According to my understanding a safe assumption about "defaults" would > mean to have the state of a fresh startup scenario replayed. More > precisely this would mean to a) read 'static' aircraft configuration > (from '*-set.xml' files), b) furtheron read stuff which had been > written into '$HOME/.fgfs/', c) afterwards read the '$HOME/.fgfsrc' > file and d) finally the given command line flags. At least this is what > I'd expect as a user .... > > To achieve such state upon "reset" you could think of a) storing every > parameter, which had been read from startup config ressources, into > reserved space in memory as "The Initial State" or b) re-read the same > set of config files and/or flags upon reset. > I guess that b) would be rather ressource-intensive, and since storing > a boiled down copy of the startup properties in memory might be rather > cheap these days, I suspect it would be the way to go.
Yeah, and indeed part of a) is already done - it's just a question of extending it to more properties / trees of properties. I can't think of any likely ways this could break existing aircraft or scripts - can you? James ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
