Hi Rob, while I do not have a non touch device, I think that using different key mapping depending on list lenght means making the UI inconsistent. Predictability is a key in UI design, so I'd propose to make the keys act precisely the same in all kinds of dialogs that contain lists.
If I understand you right, while in an e.g. waypoint list, up/down would scroll, while right would call the waypoint details and left would get the user to the buttons. When in the buttons, why not use up/down to jump through the buttons, and when he's reached the top button, jump to the tabs on top and then right/left jumps through the tabs and down opens the tab. That means kind of mimicking a mouse or joystick cursor in using the key direction to move to the next item rather than directly mapping a key on a specific action. Viele Grüße, Martin Kopplow --- Am 13.02.2011 um 17:34 schrieb Rob Dunning <[email protected]>: > I have an Altair UI question (this affects most non-touch screen devices): > > In XCSoar, when scrolling through items in a list dialog (e.g. > Waypoint lookup), should the left/right keys act as pageup/pagedn, or > should they move the cursor off the list to the buttons on the > dialog? (The left/right keys currently act as pageup/down.) > > The problem with treating left/right keys as pageup/pagedn is that > the pilot can't select and item in the list and then move the cursor > to one of the action buttons (e.g. Lookup, Rename, Delete). > > Examples: Non-touchscreen issues caused by treating left/right as pageup/down: > --> In Airspace lookup, it's impossible to hit the "Lookup" button > except on the first or the last list item because "Enter" is mapped > to different functionality > --> In Waypoint lookup, it's impossible to alter any of the filters > unless you scroll off the top or the bottom of the list > --> In Task Browser, it's impossible to Rename or Delete a task > --> In Task Editor, it's impossible to reorder the waypoints > > One solution would be to map left/right keys to the pageup/down > function for large lists like Waypoint list, but for smaller lists > map the left/right arrows to move to the next control (i.e. > "tab"). Variable behaviour is more complicated for the pilot to > undertstand, but it may be the lesser evil. > > For bluetooth joysticks, this would probably apply to the left/right > arrows on the joystick. > > Thoughts? > > Rob > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Xcsoar-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/xcsoar-user ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Xcsoar-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcsoar-user
