Lethargeek wrote: ↑Wed May 27, 2020 1:32 am
... SOME emulators might have disk/tape autostart but not all and it doesn't work properly every time. Okay, most (if not all) other emulators run a snapshot immediately as the name is selected but there are use cases when it's not desired or inconvenient so i decided to actually run it with a hotkey at the right moment.
Same about running a corresponding dux driver.
...
I'm going to go on a limb here and give you some advice on this particular issue from an UI perspective.
It seems, to me, that those particular choices you made is what is breaking the UI principle of least surprise.
When you run a command in the command line, you don't expect the parameters to not have any immediate effect.
So telling the emulator "here are the files to load" but nothing actually happening (in visual terms, i.e. no application running) it will make the users doubt if the first step was correct or they missed something.
It also makes it a lot harder to automate launching a game using your emulator. i.e. you need some way to inject key presses to it, to make it work as expected.
If you really need to not have the application start for development purposes or similar special or power user cases, then make it configurable and most importantly
NOT the default behaviour.
So provide an extra parameter, -noLaunch, -noRun, or whatever you find suitable, so that the default behaviour is what the user expects.
The developer (you) or power Users that need the special case, can then use this new parameter to force that behaviour.
My long UI 2 cents.
I hope it is helpful.