Bug 10890 - Gestures on menus should keep old menu position
: Gestures on menus should keep old menu position
Status: NEW
Product: SB Touch
Classification: Unclassified
Component: UI
: unspecified
: PC Windows XP
: -- minor (vote)
: 8.0.0
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-29 03:36 UTC by Jim McAtee
Modified: 2011-11-06 23:23 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim McAtee 2009-01-29 03:36:52 UTC
This may be a minor or non-existent concern - maybe just something I've thought about a little too much.

As of r3945, the implementation of the touch screen appears to be that no action is taken until a touch is lifted.  This is undoubtedly how it must be if gestures can be implemented at all.  The exception to this appears to be that focus is moved within menus on touch 'down'.  Again, this is how it has to be, or else it would take two full touches within a menu to select anything - one to change the selection, then one to move right.

So what happens when you execute a gesture from within a menu is that focus often moves to a new item, then the gesture is recognized and executed.  What happens later, though, is that when you return to the menu Fab4 remembers the newly selected menu position.  That could be inconvenient for someone, particularly when using the device as a controller and moving in and out of the same menus.

What I'm suggesting is that when a gesture is executed from within a menu, throw away any new menu item selection that happened at the beginning of the gesture and remember the old selection.
Comment 1 Richard Titmuss 2009-03-26 03:26:29 UTC
Tom, I think this is already fixed? Can you comment.
Comment 2 Blackketter Dean 2009-07-22 08:40:06 UTC
Moving to the product SqueezePlay because this bug appears to apply to any player based on that application code.  Feel free to move it back if it's specific to the single original product.
Comment 3 Ben Klaas 2009-07-22 08:48:29 UTC
this is a Fab4 bug
Comment 4 Richard Titmuss 2009-07-27 01:11:12 UTC
Reset priority before triage.
Comment 5 Alan Young 2011-11-06 23:23:11 UTC
Unassigned bugs cannot have a priority.