so for the next update… Im Ive implemented a couple of new things…
(not pushed yet, as would like some feedback - and I’m still complete the supercollider updates)
my issue is my ‘System’ menu is getting way to crowded, due to utilities etc.
so two changes:
Ive made is to allow sub-directories for User system command, in the same way as we have for patches. (non - contentious, just works, and you can ignore if you wish )
added Submenu for the ‘system functions’… we did discuss this before, but I wondered what your thought for the layout should be, here is what I have so far
------- System ------- Shutdown Patch Functions > Other Functions > ...users stuff.. possibly in menus --- Patches --- .... --- Patch Functions --- Shutdown Save Save New Show Favourites <--- System ...users stuff.. possibly in menus --- Patches --- .... --- Other Functions --- Shutdown MIDI Channel Info Eject Reload <--- System ...users stuff.. possibly in menus --- Patches --- ....
basic idea is Shutdown is always there… and the patching and other functions, are not really related…
(e.g. when your working a patch and likely to save, its unlikely you then want to do ‘eject’ … midi channel i think is ‘arguable’, perhaps more patching function?)
the way the code is structured it would be easy to add other menus as needed (e.g. Midi might gets its own menu)
Ideally Id like to keep the number of options quite small (ideally 4, but thats quite tricky, as shutdown is one of those) , as scrolling around the display is no fun, similarly we dont want too deep menus.
(what Ive done would allow for nested menus, but I dont think we need)
one thought I had was to also move the ‘User functions’ to a submenu , it would be nice and tidy, but the drawback is, if a user comes up with a really frequently used function (e.g. start web, or start wifi) , it means they have to go into that at startup … so as yet I have not done this.
of course now with ‘sub menus for system’ they can just place all their stuff in a sub menu called user if they wish.