From: Martin S. <Mar...@mg...> - 2010-11-02 15:16:19
|
James Turner wrote: > 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? I don't - but I'm probably not the best candidate for being questioned about this flavour of details ;-) Even if it would, having a plausible, reasonably defined and thus reproducible mechanism for the long term is probably worth a lot more than an obviously imperfect hack just to meet the needs of a few scripts (if there were the demand for such thing). The startup-scenario is a well-defined state and therefore I can't imagine why its re-instantiation could be "bad" (TM). Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -------------------------------------------------------------------------- |