Has anyone using the latest Vangelis build had issues with not being able to enable the touch navigation capabilities under User Interface/ Graphics & Usability web ui, when trying to enable V5 Keypad on left. This feature works fine on Oram (and central to my DIY build) but I can’t find any mention of this issue in the wiki or forum, so assume it’s a me problem? The buttons do not appear at all on the display and the touch display seems unresponsive, but my rotary controllers seems to be working ok.
After some further digging I found a post referring to the fact that Vangelis default to the soft keys turned off, even when enable in the web UI, and can be enabled/ disabled by tapping the top right of the touchscreen - whereby it magically appears. I assume this default behaviour has been changed as vangelisstarts up in mixer view and so on smaller screens, the mixer looks better without soft buttons using up real estate. However, even on my 7” screen, I feel there’s room to leave these enabled most of the time - would it be possible to tweak the User Interface/ Graphics & Usability web ui settings to include a sub-setting above the ‘Enable Cursor’ radio button for ‘Enable V5 keypad on startup’ - this way the show/ hide functionality still works when you need it, but the initial state can be set to display the keyboard as per the previous Oram behaviour and for those with larger screens?
1 Like
The state of the buttons is persistent so if you close down properly, they will be in the same state after restart.
Thanks for clarifying @riban … as that’s the case, wouldn’t it be better to leave the initial startup state as per Oram, but just make it clear that there is a hotspot toggle feature for those that want to use it? Maybe fewer people will be caught of when upgrading?
Webconf allows to define whether the feature is available and the position of the buttons. The ability to toggle the display of buttons from the UI by tapping the status area (top right) is new in Vangelis and is part of the change to touch support. We have removed the old touch support that provided dedicated touch workflows and now rely upon the button overlay to emulate the V5 buttons and the implicit V5 touch workflows which are mostly optional. This massively reduces the support overhead whilst delivering a perfectly operational UI to most users.
We don’t want to enable the button overlay by default as it is an option for users to toggle on/off as desired. It is now easy to toggle (if you know how) and persistent, hence we chose to make the default state hidden.
We are in the midst of documenting Vangelis, mostly in the device itself with its builtin html help but there will also be a written guide, e.g. in the wiki that describes first steps and access. This info should be in that guide.
1 Like
I guess the real issue for me was not knowing that the default had changed or the use of a touch screen hotspot had been introduced with power cycle persistence. Having the updated help guides and wiki should make this less of an issue and especially if there is an upgrade guide they details all the key improvements between oram and vangelis (which I’m discovering, there are many - so thanks to all the devs for their excellent work)
I can see how the change to V5 button emulation rather than dedicated button workflows will help reduce code complexity and testing, definitely a better solution.
1 Like