That would be HUGE! 
Some observations after further use on a V4 kit:
Add chain… > audio input
Use encoder to navigate to category Other (which doesn’t fit on screen) - the other is selected but category list does not scroll to show it.
Also, when doing the same with a mouse or touch display in a custom kit, it doesn’t scroll either. The list of delays can be dragged up or down, the category list not. And you can accidentally drag the category list to the left or right with the mouse, which should be frozen.
This is now fixed in vangelis.
[Edit] And dragging listbox with mouse now works. Fixed an issue where clicking at the end of the visible list selected the wrong entry. This lisbox behaves more like others, but I did not add gesture scrolling because it is unlikely for this list to grow too long.
1 Like
This makes me feel that switching between processor, group and parameter columns via keypad would use column focus with left/right buttons, as opposed to toggling between group selection and parameter editing with SEL/YES.
I think I agree. It feels like you are navigating a 2 dimensional grid (logically), but we also need
to consider the best workflow which may be optimal when less intuitive!
I don’t know what the best workflow is, but imho it raises the question whether category or processor selection should perhaps occupy the horizontal space with left/right buttons, so that the main column (preset or parameter group) can keep up/down buttons for itself.
And consequently, categories/processors would show as tabs below the title, with the current element centered, farther tabs cut off, and left/right arrow icons to make it clear that this is navigable.
On the other hand, I do like the possibility of drilling down to arbitrary levels with a consistent layout. E.g. when a preset group is selected in the middle column, the category list could shift out of screen to the left, with the top-level preset list taking over its leftmost column while the child preset list is now in the middle. And as a further optimization, devices could show more or fewer columns depending on their display size.
Good thing I don’t have to make hard decisions like that! You’ve got this 
My experience, based on several years of experimentation and development of interactive TV interfaces with remote controls, tells that you draw the best conclusions after actually having a group of people using and commenting a lofi usable (html or alike) mockup prototype, rather than discussing elaborated drawings/sketches. What seems usable and obvious, frequently becomes awkward when we have to do it effectively and repeatedly.
1 Like
I can easily see the benefits of that approach, but there is more workload. On the other hand, i rarely understand what it actually is that people try to describe with words, at least when it is at a certain complex level, and maybe also requires some initial understanding that i do not have.
Then again, i also feel lucky for not having a strong desire to understand everything.
Just knowing that something is going on, and that the goal of that something is to make things better, is satisfying!
1 Like
Exactly. That’s why I said the best conclusions came from people - ourselves and friends - testing actual prototypes of the menus and navigation (without the real TV functionality), instead of trying to debate between the hermetic, academic UX reasoning on one side and the product team’s abstract and confusing “I want it all” mindset on the other.
But yes, building those interactive prototypes is extra work. We used to do it only for the key, higher‑level decisions about the interaction model. With great benefit.
i agree
But i also think that it is sort of what is being done in this dev team (except the prototypes are not mock-up but functioning (to a degree) code. There is a lot of UI being coded, then uploaded and turned into UX for people like me. And i comment on that and sometimes UI changes or shifts because of our interaction.
Then in some cases - someone has a dream , post’s it here, and i try to understand the dream and quite often fail to do it. But i am also left with a feeling that others understands and that there are only some who don’t. In those cases i am often served some new/altered UI in the next couple off updates as a result of those conversations that i do not understand (and a lot of work i guess). Then i play around with it, it becomes UX and there is feedback.
1 Like