Re: [UX advise] Key navigation in ValueSet controls

Hi Matteo,

so, took me a while to find the courage to read that :) But good
observations these are.

Anyway, ...

> Is this behavior the expected/commonly accepted one?
> I would like to propose:
> * left/right motion should not wrap around from first to last (or last
>  to first) item. Moving through lines is fine (behavior similar to
>  moving through text), although we can also just stay on the same line
>  and stop at its borders.

Makes sense to me. Although, of course the decision depends on whether
we want to make it fast to go to an arbitrary position without much
exactitude or whether we want to make it fast to go to the exact
start/end. Your proposal seemingly aims for goal #2.


> * up/down should not wrap around. If pressing up on a middle column of
>  the first line, then it moves to the first item. If pressing down, it
>  should move to the column below if present, to the last item
>  otherwise.

From my Western perspective that does make sense. However, I fear,
such behaviour might be unexpected in some cultures (that use
top-to-bottom scripts). Any experts?


>  Please note that this is not similar to up/down navigation in text in
>  writer (since I propose to move to first/last item if we cannot move
>  of a whole line), but other application (e.g. thunderbird) behaves in
>  this way. At least it allows to display (and make the user aware of)
>  partial final lines.
> * page up/down should mimic the behaviour of up/down keys: move in the
>  same column when possible (even if the distance is less than a page)
>  and, when pressed again and no motion in the current column is
>  possible, reach the first/last element. I don't know if disabling
>  navigation when key-modifiers are pressed makes sense.

Makes sense. I guess, modifiers should be allowed (but not modify
anything), in all cases where that's possible without unintended
consequences.


> * If "none" item is present, then it could be accessed only from the
>  first item by pressing any of left/up (also page up/home ?) keys.
>  When selected, it can be exited only by pressing right/down (also
>  page down/end?) keys, but always lead to the first item.

Makes sense.

> * Return key behavior: at least it should not close the color
>  configuration window, but my guess is that's a misconfiguration of
>  the specific instance of ValueSet.

Not entirely sure about this one, although probably most people would
want to use Return and Tab the same way (i. e. to get to the next
widget and select a colour).


Astron.