Re: irritating bug in Keyboard Preferences when seeking to the next command by hitting a keyboard character

4 messages Options
Embed this post
Permalink
Ed Musgrove-2

Re: irritating bug in Keyboard Preferences when seeking to the next command by hitting a keyboard character

Reply Threaded More More options
Print post
Permalink
The terms might be getting a little bit confusing. There is a panel to the
left of the window which presents the user with a choice of which preference
pane to display -- I have been installing that "the panel to the left"; the
right-hand side of the window has a drop-down control which filters the list
of shortcut keys -- I will call that "the drop-down control"; below the
drop-down control is a list -- I have been calling that "the panel to the
right".

Any one of these three items might have focus. I have been totally ignoring
any case where the drop-down control has focus. That is why, in every single
test, I have specified first clicking on the column header (assuming this
would give focus to the panel to the right). Unfortunately, this also seems
to change the sort order of the list in the panel to the right (from
top-down and bottom-up or the reverse as appropriate). This does not happen
on Windows. Does it happen on Linux?

I have also been totally ignoring any use of the <Tab> key.

--Ed


> -----Original Message-----
> From: Gale Andrews [mailto:[hidden email]]
>
> That's why I think when you tab from Category we should force the first
list
> item to be selected. That is analogous behaviour to tabbing from a tab in
the
> Preferences tree into the pane for that
> tab - the first item in that pane is selected i.e "really selected".
>
[Ed:]
I agree that if the drop-down control has focus, the tab key should select
the first item on the list.

> Having up/down wrap to bottom/top of the list would be nice but HOME and
> END do appear to work on Windows/Linux.
>
>
> > Also of note (possibly) is that pressing tab moves focus from the list
> > to the text box, but pressing tab while the text box has focus inserts
> > "tab" into the text box (which makes sense). There appears to be no
> > way to move focus from the text box with the keyboard. Clicking the
> > "Set" button leaves the text box with focus.
>
> Similarly on Linux, pressing TAB when you have your shortcut entered in
the
> box just enters TAB into the box. And we just removed the accelerator from
> "Set" because that does not work either. I can see no way round that. As
> soon as you press ALT with focus in the box to try and move to another
> button and back, the input is cleared from the box.
>
> So it seems a keyboard user on Mac/Linux can only change
> preferences by saving, editing and re-loading the xml file.
>
> Tabbing from box to "Set" works on Windows.
[Ed:]
On Windows, the tab key should not be allowed as a shortcut key. The
OnKeyDown function should immediately examine the event and determine if it
is the tab key (or any other inappropriate key); if so, it should exit
immediately passing the event up the event handler chain. I get the
impression from your above paragraph that the <ALT> key works the same way
in Linux as the <TAB> key does in Windows, is this accurate? Does the Mac
have a keyboard shortcut which brings focus to the next "thing" (button,
list box -- whatever)?



------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Bill Wharrie

Re: irritating bug in Keyboard Preferences when seeking to the next command by hitting a keyboard character

Reply Threaded More More options
Print post
Permalink
Some javascript/style in this post has been disabled (why?)
[snip]

[Ed:]
On Windows, the tab key should not be allowed as a shortcut key. The
OnKeyDown function should immediately examine the event and determine if it
is the tab key (or any other inappropriate key); if so, it should exit
immediately passing the event up the event handler chain.

And the same should happen for Mac and Linux, IMO.

I get the
impression from your above paragraph that the <ALT> key works the same way
in Linux as the <TAB> key does in Windows, is this accurate? Does the Mac
have a keyboard shortcut which brings focus to the next "thing" (button,
list box -- whatever)?


On Mac, the TAB key is used to move keyboard focus from one element to the next. My understanding about Gale's mention of the ALT key is that the ALT key is used for the "accelerator" functions (e.g. ALT-S "presses" the "Set" button). On Mac, that would be OPTION-S, I assume. With focus on the text box, pressing ALT or OPTION clears the text box in preparation for accepting whatever key combination the user is about to enter. On my Mac pressing SHIFT, CTRL, or COMMAND also clears the text box if it has focus. Why it does this is a mystery to me. Why not wait until an actual, valid key combination is pressed to update the text box? This still means that *all* accelerators would not work when the text box has focus, or the user would not be able to set a shortcut of the form ALT-<key> or OPTION-<key>.

-- Bill

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Gale (Audacity Team)

Re: irritating bug in Keyboard Preferences when seeking to the next command by hitting a keyboard character

Reply Threaded More More options
Print post
Permalink

| From Bill Wharrie <[hidden email]>
| Sun, 18 Oct 2009 16:05:24 -0400
| Subject: [Audacity-devel] irritating bug in Keyboard Preferences
| when seeking to the next command by hitting a keyboard character

> > I get the
> > impression from your above paragraph that the <ALT> key works the  
> > same way
> > in Linux as the <TAB> key does in Windows, is this accurate? Does  
> > the Mac
> > have a keyboard shortcut which brings focus to the next  
> > "thing" (button,
> > list box -- whatever)?
> >
>
> On Mac, the TAB key is used to move keyboard focus from one element to  
> the next.

Yes that use is universal, cross-platform.

> My understanding about Gale's mention of the ALT key is that  
> the ALT key is used for the "accelerator" functions (e.g. ALT-S  
> "presses" the "Set" button). On Mac, that would be OPTION-S,
> I assume.  

Yes, ALT operates accelerators on Linux almost the same
way as on Windows. Linux is not as nice IMO for menu
behaviour as you have to keep the ALT key held down
with the relevant character to access menus with the
keyboard; on Windows, you only have to press ALT then
the character.

Neither OPTION or ALT on Mac work with accelerators to
the best of my belief, and wxMac strips the accelerators
out. So as far as I know, Mac users will not see any
underlinings in the Preferences strings and buttons, even
now they've been added.  

 
> With focus on the text box, pressing ALT or OPTION clears the text box  
> in preparation for accepting whatever key combination the user is  
> about to enter. On my Mac pressing SHIFT, CTRL, or COMMAND also clears  
> the text box if it has focus. Why it does this is a mystery to me. Why  
> not wait until an actual, valid key combination is pressed to update  
> the text box? This still means that *all* accelerators would not work  
> when the text box has focus, or the user would not be able to set a  
> shortcut of the form ALT-<key> or OPTION-<key>.

That's why we removed the accelerator from "Set".



Gale


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Ed Musgrove-2

Re: irritating bug in Keyboard Preferences when seeking to the next command by hitting a keyboard character

Reply Threaded More More options
Print post
Permalink
In reply to this post by Ed Musgrove-2
FYI...

--Ed


> -----Original Message-----
> From: Gale Andrews [mailto:[hidden email]]
>
> Yes, ALT operates accelerators on Linux almost the same way as on Windows.
> Linux is not as nice IMO for menu behaviour as you have to keep the ALT
key
> held down with the relevant character to access menus with the keyboard;
> on Windows, you only have to press ALT then the character.

[Ed:]
Vista now operates like Linux -- you have to hold down the ALT key while
pressing the accelerator key. I would guess Windows 7 is the same.



------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel