Of course.
This is what the .cfg file looks like when you open the settings manager for the first time and save without touching anything.Quote:
What's in the files is
Can't reproduce this here; all changes apply as expected. Since this version includes a settings.dat file, it is portable and therefore the settings manager will only read and write serenity_settings.cfg from its own directory. Any chances you have two installs with two configuration files after upgrading, and are looking at the wrong one?Quote:
EDIT: nvm, I found the issue. I had to use the old settings manager. The one included in this version doesn't update serenity_settings.cfg file!
By the way, the only modifications I made to the manager are editing the URL in the About window and fixing the PE checksum. The latter isn't even checked for executables, but I thought correcting it was good practice and might possibly help somewhat with issues under Windows 10.