Re: on application focus navigation (was: On ctrl-tab)

[Jud Craft <craftjml gmail com>]

On another note related to the widget-group problem, consider GEdit
and Rhythmbox, specifically their toolbars, and arrow key navigation
of a toolbar.



In GEdit, I can enter the toolbar using tab and ctrl-tab.  I can only
exit it using tab (ctrl-tab, which should get into anything, gets
stuck in it for some reason...).  I can also use the arrow keys, which
is pretty cool, but if you're moving through fields with ctrl-tab, I
don't want to change over to a new shortcut.

In Rhythmbox, I can enter the toolbar using tab.  But, you can't
navigate it with either tab or ctrl-tab!  You have to use the darn
arrow keys only!



Again from the previous mail, I think it would more consistent if one
blessed focus shortcut [in this case ctrl-tab, at least] could make it
through any field and any group.

Tab is a useful shortcut to quickly change fields, and I understand
needing a non-textentry-conflicting shortcut.  But whatever this
shortcut is, it, at least, should be able to access anything.  That's
my opinion, it may be wrong.

It is highly lovely and convenient to be able to move through every
field with the same method.  [Especially with the GNOME Sticky keys].
I'm okay with different quick-and-easy methods (Tab when text-entry is
not a problem, arrows in a toolbar*), but if there's going to be a
super-navigator shortcut, then it needs to cycle through every field.



*And since even this causes problems when your toolbar contains
anything except buttons [textboxes (which lock left and right arrows),
volume meters and dropdownlists (which lock up and down)], it would
almost be simpler if this wasn't an option either.

The only thing more frustration than multiple options for keyboard
navigation, are multiple options that only work at certain times.
It's frustrating enough that Tab has text-entry conflicts.

The arrow-key conflicts with text-entry and dropdowns only make GNOME
keyboard navigation more complex.  I know they were meant to make it
simpler (very easy to move between elements), but in anything but a
static list of elements, it's a pain to keep track of "is this widget
going to eat my keyboard navigation?"