I started to look at this but immediately hit a snag / question. To shutdown, I need to show the V5 buttons and so the last state may always be in this mode, even if most of the time the user prefers not. Any suggestions?
I had previously decided to not show V5 buttons by default because you will usually start in the mixer view which is an operational view that may benefit from full screen.
Hm. When using the 4th encoder or an equivalent configured button, with long press, it shows the shut down screen without extra menu. So no usual V5 buttons need to be displayed in this case. Does this method help?
Not on a touch-only, with no encoders!
On those systems we used to have the option to tap/click the top header status bar to open the admin menu and choose shutdown. It seems that isnât working (or Iâm doing it wrong) with the dynamic switching to V5 buttons on screen.
The point of this change was to replace all those touch-only workflows to reduce support burden. If we get feedback that fast access to a particular touch-only workflow is required, we can consider adding it.
Understood, in that case an option would be not to save the last state but just respect the/a setting to set the startup state.
All three (short, bold, long) triggers of topbar are used to toggle mixer/launcher. I have been trying to reduce the use of both bold and long because it confuses users. We could use bold/long to show a grid of shortcuts to various screens / actions. This could even be configurable so users can have quick access to match their workflow. I will try to build something to test.
Okay - thanks to inspiration from @jawn I have implemented a fast navigation panel. Bold/long press the topbar to show a grid of actions, mostly short press navigation but also power off / bold press to reboot.
I would say: If you trigger the onscreen buttons manually, they remain always on, if you donât, they reveal themselves whenever they are needed.
Especially for custom builds that rely on V5 buttons it might be preferred to also show them on startup and the screen may be configured to meet the requirements.
This is a good improvement!
To make it even better, my brain would prefer not to confuse it with the add instrument screen.
E.g. by adding a title to both screens.
On the other hand I really appreciate unifying the appearance of different screens. Maybe a title would help (âAdd Chainâ/âFast Navigationâ).
Done!
My brain is glad now 
However, when shutting down I get hangs now with the Powering Off screen and this log:
Mar 19 19:54:24 zynthian startx[914]: ERROR:zynthian_gui.cuia_thread_task: CUIA âzynswitchâ failed with params: (3, âSâ)
Mar 19 19:54:24 zynthian startx[914]: Traceback (most recent call last):
Mar 19 19:54:24 zynthian startx[914]: File â/zynthian/zynthian-ui/zyngui/zynthian_gui.pyâ, line 2630, in cuia_thread_task
Mar 19 19:54:24 zynthian startx[914]: self.zynswitch_short(i)
Mar 19 19:54:24 zynthian startx[914]: File â/zynthian/zynthian-ui/zyngui/zynthian_gui.pyâ, line 2238, in zynswitch_short
Mar 19 19:54:24 zynthian startx[914]: self.screens[self.current_screen].switch_select(âSâ)
Mar 19 19:54:24 zynthian startx[914]: File â/zynthian/zynthian-ui/zyngui/zynthian_gui_confirm.pyâ, line 111, in switch_select
Mar 19 19:54:24 zynthian startx[914]: self.callback(self.callback_params)
Mar 19 19:54:24 zynthian startx[914]: File â/zynthian/zynthian-ui/zyngui/zynthian_gui_admin.pyâ, line 780, in power_off_confirmed
Mar 19 19:54:24 zynthian startx[914]: self.last_state_action()
Mar 19 19:54:24 zynthian startx[914]: File â/zynthian/zynthian-ui/zyngui/zynthian_gui_admin.pyâ, line 788, in last_state_action
Mar 19 19:54:24 zynthian startx[914]: zynconf.save_config({âZYNTHIAN_TOUCH_SHOWNâ: zynthian_gui_config.touch_shown})
Mar 19 19:54:24 zynthian startx[914]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Mar 19 19:54:24 zynthian startx[914]: AttributeError: module âzyngui.zynthian_gui_configâ has no attribute âtouch_shownâ
Above is the log after all chains are first removed, then shutting down. Also hangs if chains not removed. Tested on V4 kit.
Version info
zyncoder: vangelis (c3b7fcf)
zynthian-ui: vangelis (5dd2afc)
zynthian-sys: vangelis (a9e7833)
zynthian-data: vangelis (e739e9a)
zynthian-webconf: vangelis (88bded4)
P.S.: and wonderful to see Vangelis on the Zynthian! A big milestone.
Fixed.
Thanks, reboot and shut down now working properly.
If like me, Admin > Update software didnât work it is caused by the same issue above. Workaround: use Webconf > Software > Update instead.
I couldnât help noticing something else 
Fast navigation > Power (Reboot) shows âDo you really want to power off?â 
So either the icon title should be changed or it should call the reboot.
Admin > Reboot shows âDo you really want to reboot?â 
Short press to power off. Bold press to reboot. I realise the legend text might be confusing. Any suggestions for improvement?
I see itâs by design.
I feel it kind of breaks the easy learning curve of having this screen in the first place.
Options:
This is the idea I had. I have it working but there is a merge conflict I need to resolve so it might be tomorrow before I can roll that out. It is a neat solution. The reason for having the power option in the fast actions menu is because we want to encourage users to close down properly, with the benefits of saved last state, etc. I find it a bind to menu dive for this on a touch-only screen.
[Edit] This is now deployed. There is a single âPowerâ entry in admin menu and a single âPowerâ button on the fast launcher. These show a screen with 3 buttons:
Pressing any of these buttons triggers the corresponding action immediately. This is a neat workflow that many will be familiar with with desktop OS shutdown / reboot options.
I also fixed segfaults in the audio clip launcher and zynsampler.
