Support and General Use > User Interface and Voice

how should the touchpad buttons work?

(1/1)

JdGordon:
I've just commited work so the 2 touchpad almost-targets have an extra 21 buttons now (9 press areas and 12 slide-button-transitions (move from left to centre, or center to rioght, etc) so now we need to decide how each screen should work...

currently, in the lists middle up/down/left/right are directions, center button is select. top left is menu...

almost every other screen wont work properly yet... so suggestions?

remember this is only for the fake touchpad buttons so the target makes no difference (and you cant have combos other than the simple movement transitions...)..
ideally the entire UI should be useable with only the touchpad (and then depending on the target maybe with the real buttons without the touchpad... but thats another topic)

Llorean:
Question: Can buttons be held? (Can long-tap of center give the context menu?) or will we need to use transitions for such things?

Though I guess "Center->Up" works.

Also, I realized my math is poor, we have a lot more than 21, since i assume "Center->Up" can be handled separately from "Up->Center". For some silly reason I just thought of them as being a single transition per interface, not two. So we actually have 9 press areas plus 24 transitions. Though I think in many cases we'll want duplication (for example, Center->Up, and Bottom->Center could do the same think, so they just need to make an upward motion in the general area of the center of the screen).

JdGordon:
yes buttons can be hekd. but its either a hold or a transition.. not both..

Llorean:
Makes sense. So, 18 actions from single buttons or button holds, 24 actions from transitions. You can assign 42 actions per screen before you even get to hardware buttons.

Navigation

[0] Message Index