Filename of OoliteDefaults.plist has been changed to "oolite.plist"

[phkb]

Was this intentional? I'm assuming it was one of the most recent merges (#680 maybe?) that did this, but given we only just changed the name in v1.92, is it necessary to change it again?

[phkb]

Actually, I just read the full notes on #680 and can see that @mcarans mentioned that it was necessary. Unfortunate though. Is there any way we can migrate settings from the old file? I can just see there being frustration and confusion if players update to the latest version and all their joystick and keyboard settings have to be re-entered.

[mcarans]

I don't know why GNUstep doesn't honour the CFBundleIdentifier when Resources is moved to a different folder to the executable. See this discussion about locating the Info-gnustep.plist file (which is in Resources): gnustep/tools-make#73. I made CFBundleIdentifer equal the oolite executable name as that seems to be the only way to get it to be consistent unfortunately.

The old file with existing settings can be renamed. This would be easy to do in the Linux run_oolite.sh but Windows doesn't have a startup script. Maybe this could be done in main.m, but is it ok to rename a user's file without their knowledge? Maybe it's best to just document that renaming is needed and show how? What do you think?

[LW-archlinux]

copying or renaming OoliteDefauts.plist to oolite.plist works fine.
Just put a note about the change in the announcement section of the forum and let users handle it themselves ?

[oocube]

A bit late for my taste. This would mean a user downloads and installs the new version, then finds out it does not work to expectation. Maybe he recreates all the settings, maybe he gets frustrated. Then searches for support, finds the forum and starts a thread - just to be pointed to some banner message.

Is there no way to prevent that story - maybe with an early warning message on Oolite startup?