- August 25, 2017 at 5:49 am #22299
The amount of the changes in v17 really made me hesitated. I didn’t begin the testing until now.
A configuration name must be valid because it’s a folder name now.
This is really a bad news for me.
I hope my late suggestion still can be considered.
My thought is:
Let the folder names be just folder names, e.g. cfg1, cfg2, cfg3, …
And use a (ini) file. In the file, the folder names correspond one-to-one with the configuration names:
Thus, almost any character can be used in a configuration name.August 25, 2017 at 12:56 pm #22301
That is a good idea, but I wish you could have written your idea before the official release of v17.0. I might add that feature in future versions.
You must be logged in to reply to this topic.