* Melchior FRANZ -- Wednesday 09 August 2006 19:09:
I think we should also save aircraft specific settings
in this file
An alternative would be to save aircraft specific stuff in
getprop(/sim/fg-home)~/~aircraft_name~.xml, that is:
each aircraft saves its settings in its own file. Would this
Melchior FRANZ wrote:
* Melchior FRANZ -- Wednesday 09 August 2006 19:09:
I think we should also save aircraft specific settings
in this file
An alternative would be to save aircraft specific stuff in
getprop(/sim/fg-home)~/~aircraft_name~.xml, that is:
each aircraft saves its settings in
* Josh Babcock -- Wednesday 09 August 2006 20:03:
Melchior FRANZ wrote:
getprop(/sim/fg-home)~/~aircraft_name~.xml, that is:
Well, I already use /sim/model/name/ for aircraft specific stuff just
to keep things neat.
Yes, it's a kind-of standard.
For that reason I like the latter idea,
* Josh Babcock -- Wednesday 09 August 2006 20:16:
My point was that if you automatically store everything in
/sim/model/name you may grab a lot of stuff that doesn't need to be
stored. We need a way to designate what gets stored and what doesn't.
I was actually suggesting the autosave.xml
On Wednesday 09 August 2006 18:09, Melchior FRANZ wrote:
If someone wants to save e.g. frequencies, then he should save
them in
/sim/model/foocopter/instrumentation/comm/frequencies/selected-mhz (or
something) and on startup copy the frequencies to their
respective addresses.
Melchior FRANZ wrote:
* Josh Babcock -- Wednesday 09 August 2006 20:16:
My point was that if you automatically store everything in
/sim/model/name you may grab a lot of stuff that doesn't need to be
stored. We need a way to designate what gets stored and what doesn't.
I was actually
AJ MacLeod wrote:
Personally I don't think we need a separate file for each aircraft, but I
don't have any particularly strong feelings either way on that one. I
suppose it would make it very easy to return any aircraft model to standard
state..
It would be not too difficult to delete the
7 matches
Mail list logo
