Re: [Flightgear-devel] C172P version in 2016.3.1 broken ASI?

[Rebecca N. P. <reb...@zo...>]

On 20/10/16 23:47, Denk Padje wrote:
> This is caused by old incompatible .fgfs/aircraft-data/c172p.xml data file.
> 
> 1) FG should save data files also when a user presses the X button in
> the window decoration, not just when the user goes to File > Exit >
> Yes.

Agreed, though I don't know how easy it would be.

> 2) When FG initializes itself after the version number has changed, it
> should either delete old data files (because new aircraft might be
> incompatible)

Probably a bad idea to do it to everything: it's likely to needlessly delete
settings more than it avoids bugs.  I'd instead suggest that aircraft making
an incompatible change add a version tag to their data files and discard
data files without it.  (We could also have a "delete data files on aircraft
upgrade" (not core-FG upgrade, aircraft aren't required to have the same
release cycle as core FG) *option*, but the aircraft developer should be
able to choose whether they want it.)

(and yes, I do also dislike that we throw away core-FG settings on upgrade -
that actually hung my system once, because the defaults used to need more
RAM than I have)