* Durk Talsma -- Wednesday 21 September 2011:
> Just a quick question: Is this documented somewhere?
Don't think so. Only in the code, that is.
> If not, I might start a short wiki page documenting the logic behind
> "archieve", "userarchieve", and the interactions with the nasal system.
"userarchive" simply marks what gets written to $FG_HOME/preferences.xml
and loaded next time from there (if and only if /sim/startup/save-on-exit
is true). It's mainly thought for persistent GUI settings. It should not
be set by aircraft, *ever*. (Needless to say that some aircraft do it
anyway.[0])
"archive" is used by simgear/props_io.cxx -> writeProperties(). This
function either saves a whole property tree or only those properties
with set "archive" flag. This is used by fgSaveFlight(), which should
only save the properties that are to be restored when a saved flight is
loaded again via menu. This was broken for so long, until everyone
had forgotten what "archive" was about and on which properties it
should be set. It's basically what ac_state.nas does in pure Nasal,
once again ...
m.
[0] 727-230 737-300 777-200 787 ATC B-1B CRJ-200 MPCarrier OV10 Rascal
SenecaII bf109 ch53e dhc8 spitfireIX
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
