Thank you, Ralf!
I like your idea of presets. Let me introduce you to my concept of implementing the promised customization and a form of 'presets'. As I want to keep the program lean and reliable, the most efficient solution seems to be an optional INI file, that will include all the customized settings. Activating a 'preset' will be as simple as replacing that file, sharing will be easy too. What do you think about this approach?
As a side note, Randomizer received a small update. It now displays a confirmation message after completion. You can re-download it from the same URL I gave earlier and overwrite the old one if you had downloaded that.
Thank you for trying to make the Randomizer customizable.
I agree that the Randomizer should be kept simple and executable with one mouseclick. So having an INI file would achieve that very simply.
On the other hand having in mind presets for small, medium and large airports it might get confusing. That would lead to 9 combinations of SID and STAR settings thus 9 optional INI files. So before each run of randomizer.exe I would have to copy and rename one of those optional INI files as the "active" INI file. Airport specific settings would not really work like this.
Anyway I would be happy to have this option.
A more sophisticated solution might look like this:
To have separate Setting / INI- files for SIDs and for STARs. Then to have some kind of an optional User Interface where you can choose a predefined setting / INI-file for the departure and a predefined setting / INI-file for the destination. Maybe simply by opening a Windows Explorer Window where the files could be chosen.
I hope I made this comprehensible. I don't have the knowledge to estimate if this is possible and how complicated that would be for you to implement.
Thank you very much for your efforts!