antconc_settings.ant behaviors under Windows 10

[Hongyin Tao]

Under Windows 10, one can click on the saved setting file and start the AntConc program with the settings specified in the file. However, if the settings file name (excluding the extension) is anything other than the standard one, the saved settings will not take effect by clicking on it directly. If the same directory has one with the standard file name, click on the one with a non-standard name, the one with the standard name will take effect. Thus, in the same folder where both setting files exist,

a) antconc_settings.ant (standard)

b) antconc_settings_Keywords.ant (non-standard)

click on b) will not work, and the settings in a) will take effect instead.

However, if one starts AntConc from scratch, and import an *.ant setting file, then any saved settings in any setting file name will take effect as intended; but the downside of this is that the user has to look for the *.ant file location, which may take a bit of time as it can be deeply embedded somewhere in the system - away from where the AntConc.exe is located.

Ideally it would be good for the user to be able to click on any *.ant file name and let the save settings take effect.

My temporary workaround, when multiple settings may be needed,  is to save the different settings with different .ant file names, but change the one I want to use to the standard name and click on it.

Does anyone have a better solution?

Hongyin