The idea is to handle multiple instances smoothly.
If a user starts MIOS Studio as they do now, it will be the same as now: it remembers midi in/out devices and path to hex file.
If a user starts MIOS Studio with an argument say “project1” then the following settings are saved somewhere to be loaded next time MIOS is invoked with “project1”:
screen position and size of window
size of all horizontal dividers
midi in/out devices
path to hex file
any other settings to remember?
perhaps the argument e.g. “project1” appears in the window title
The idea is the user saves shortcut(s) to various instances for simultaneous or consecutive uses: e.g I am working with a project that makes big use of the terminal on a particular virtual midi port, at the same time as controlling another midibox that uses the virtual keyboard but not much terminal,etc,etc.
I agree that such customized setups are useful and I’ve also did some preparations to handle this, just only the store/restore functions have to be implemented.
But concurrent usage of multiple setups is not considered and the implementation would result into a major code rework which I would like to prevent (to avoid an unnecessary high complexity)
Instead, multiple instances of MIOS Studio have to be opened - does this sound acceptable?
Instead, multiple instances of MIOS Studio have to be opened - does this sound acceptable?
Yes, what I’ve suggested would result in being able to have separate icon’s to startup the separate instances (each with their own stored saved properties as I described).
To set up an instance, the user would create an icon/shortcut then edit the command line with an instance name as argument.
I imagine behind the scenes a folder with the settings files for each instance which could be copied/deleted/edited if required.
Yes, command line options would probably really a better solution, because I noticed that otherwise there are more GUI enhancements required than expected.