Suggestion: Keeping old options when installing new build
Moderator: Oberlus
- Cpeosphoros
- Space Kraken
- Posts: 124
- Joined: Sat Jan 30, 2016 11:29 am
Suggestion: Keeping old options when installing new build
Would it be possible that the installer give the option to not overwrite config.xml?
IMO, it's annoying having to reconfigure everything after installing the builds - or, having to save old config.xml and copying it over the new one, with the risk of mangling any change to the file format the new build may have included.
IMO, it's annoying having to reconfigure everything after installing the builds - or, having to save old config.xml and copying it over the new one, with the risk of mangling any change to the file format the new build may have included.
All contributions are released under GPL or LGPL v2 or later, or under appropriate Creative Commons licence, consistent with project guidelines.
- adrian_broher
- Programmer
- Posts: 1156
- Joined: Fri Mar 01, 2013 9:52 am
- Location: Germany
Re: Suggestion: Keeping old options when installing new buil
No. Any installer for any software changes the system only and not the local users, because this opens a whole new set of problems.Would it be possible that the installer give the option to not overwrite config.xml?
If you want to keep certain configs, use the persistent_config.xml instead.
Resident code gremlin
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz
- Cpeosphoros
- Space Kraken
- Posts: 124
- Joined: Sat Jan 30, 2016 11:29 am
Re: Suggestion: Keeping old options when installing new buil
I didn't know I had that option.adrian_broher wrote:If you want to keep certain configs, use the persistent_config.xml instead.
All contributions are released under GPL or LGPL v2 or later, or under appropriate Creative Commons licence, consistent with project guidelines.
Re: Suggestion: Keeping old options when installing new buil
It's probably not that well documented at the moment, being more some kind of stop-gap solution/hack which isn't particularly user-friendly anyway. The perks of an open source project in alpha phase...Cpeosphoros wrote:I didn't know I had that option.
- Cpeosphoros
- Space Kraken
- Posts: 124
- Joined: Sat Jan 30, 2016 11:29 am
Re: Suggestion: Keeping old options when installing new buil
If I understood it right, from the changelog and reading the code, persistent_config.xml should be in the same directory as config.xml, and contain any options I don't want to be changed by new builds. Is that correct?Vezzra wrote:It's probably not that well documented at the moment, being more some kind of stop-gap solution/hack which isn't particularly user-friendly anyway. The perks of an open source project in alpha phase...Cpeosphoros wrote:I didn't know I had that option.
All contributions are released under GPL or LGPL v2 or later, or under appropriate Creative Commons licence, consistent with project guidelines.
- Geoff the Medio
- Programming, Design, Admin
- Posts: 13603
- Joined: Wed Oct 08, 2003 1:33 am
- Location: Munich
Re: Suggestion: Keeping old options when installing new buil
I think it will also override any options saved when you modify them in the UI, resulting in the change being reverted the next time you run the program. It might also prevent (runtime-modified) options from propagating from the client to the server.
- Cpeosphoros
- Space Kraken
- Posts: 124
- Joined: Sat Jan 30, 2016 11:29 am
Re: Suggestion: Keeping old options when installing new buil
Right, so, if I change some option I should go to config.xml and move it again to persistent. Not so much work, considering I'm doing that now with code snippets.Geoff the Medio wrote:I think it will also override any options saved when you modify them in the UI, resulting in the change being reverted the next time you run the program. It might also prevent (runtime-modified) options from propagating from the client to the server.
All contributions are released under GPL or LGPL v2 or later, or under appropriate Creative Commons licence, consistent with project guidelines.
Re: Suggestion: Keeping old options when installing new buil
AFAIK yes. And what Geoff said.Cpeosphoros wrote:Is that correct?
- Geoff the Medio
- Programming, Design, Admin
- Posts: 13603
- Joined: Wed Oct 08, 2003 1:33 am
- Location: Munich
Re: Suggestion: Keeping old options when installing new buil
Or just edit persistent_config.xml directly.Cpeosphoros wrote:Right, so, if I change some option I should go to config.xml and move it again to persistent.
- Cpeosphoros
- Space Kraken
- Posts: 124
- Joined: Sat Jan 30, 2016 11:29 am
Re: Suggestion: Keeping old options when installing new buil
On editing config.xml, is it possible/planned that the Objects view's columns' width would be editable inside the UI? The config.xml has the options to adjust it, but it's kinda akward to do that from a config file, instead of simply dragging it in the UI directly.
All contributions are released under GPL or LGPL v2 or later, or under appropriate Creative Commons licence, consistent with project guidelines.
- Geoff the Medio
- Programming, Design, Admin
- Posts: 13603
- Joined: Wed Oct 08, 2003 1:33 am
- Location: Munich
Re: Suggestion: Keeping old options when installing new buil
Would be nice / should be done, but I don't plan on doing it any time soon.Cpeosphoros wrote:...is it possible/planned that the Objects view's columns' width would be editable inside the UI?
A similar issue is the current inability to manually adjust the size of the fleets and ships lists in the FleetWnd. Someone was working on it a while ago, but never got it to a useful / acceptable state.