New installation of XY does not load a saved config

[Jeff Bellune]

Beta version 6.70.0007

1. Delete existing XY folder (back it up first!).
2. Extract noinstall .zip to old location of XY
3. Launch and unlock XY.
4. Close and re-open XY.
5. File>Settings>Load Configuration.
6. Choose an .ini file from old installation's backup folder.

Actual result:
The old .ini settings are not applied. However, the name of the config file in the Title Bar updates as expected.

Desired result:
Application of the old .ini settings.

Workaround:
Copy the old .ini file from the backup folder to the new program folder. This overwrites the newly "loaded" .ini file and updates XY properly.

Notes:
I have not tried this with any other version, beta or release, so I don't know if it's a beta thing or not.

I would like to see a simple "Restore backup" operation available, which would include the catalog, udc and cks files along with the config file.

EDIT: After overwriting, the "Load Configuration..." operation works as expected from that time forward.

-Jeff

[admin]

Look at the title bar of the Load Configuration dialog. INI files are officially supposed to be located in the app path.

I guess this converts your bug report into a wish, right?

[Jeff Bellune]

Look at the title bar of the Load Configuration dialog. INI files are officially supposed to be located in the app path.

I guess this converts your bug report into a wish, right?

Actually, I think it converts it into an I-need-better-glasses report.

But yes, a wish will do nicely, thank you.

-Jeff

[admin]

Look at the title bar of the Load Configuration dialog. INI files are officially supposed to be located in the app path.

I guess this converts your bug report into a wish, right?

Actually, I think it converts it into an I-need-better-glasses report.

But yes, a wish will do nicely, thank you.

-Jeff

Did it. With a slight twist:

Code: Select all

    + Menu File | Settings | Load Configuration...: Now can can load a 
      configuration file (*.ini) from anywhere (not just from application 
      path as it has been before)! However, to keep things in one place, 
      a copy of that file will be auto-created in the application path 
      (no overwriting will happen), and that copy will be used as the 
      new configuration file.