Re: [Audacity-devel] keyboard interaction bug in 1.3.4rc0.0
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Martyn S. <mar...@go...> - 2007-10-18 00:25:03
|
Hi David, and the rest of you, This was a useful response and gave me a few clues where to look for the slider stuff. Elsewhere in Audacity (eg in the prefs), in a drop-down list box, left/right arrow keys do the same as up/down arrow keys, and usefully I think. Is it OK to have that behaviour? I have that implemented here at the moment. The only other sensible thing to do with a left/right arrow key in this situation (I think) is to move to the next control, but I don't think that's as useful (and I can't figure out how to do it!). What do you think? I currently have fixed: DeviceToolbar: obeys Left/Right/Up/Down arrows for selecting things. MixerToolbar: sliders obey Left/Right/Up/Down/PageUp/PageDown. SelectionBar: Project Rate drop-down obeys Left/Right/Up/Down arrows for selecting things and allows L/R arrows to start editing. TranscriptionToolbar: slider obeys Left/Right/Up/Down/PageUp/PageDown. Most recent version at http://mjshaw.at-uclan.com/audacity.zip for testing. Any feedback before I commit it? I currently have still broken from previous versions: Mixer Toolbar sliders move when Device Toolbar selections made (I'm not sure if this is related to what I've been doing). No tracks on screen then use the arrow keys ding: not a (closely) related problem, I feel. I think it should be caught in AudacityProject::TryToMakeActionAllowed, bit I'm not sure. James? Not such a big problem now since you don't end up there as often? Maybe I'll do a clean-up and commit it tomorrow, if there's no major objections. TTFN Martyn David Bailes wrote: > Hi Martyn, > > a) and b) are OK. > > 1) For a horizontal slider, normally you can increment/decrement it by > either right/left arrow keys, or up/down arrow keys. (If you open > mouse properties in the Control panel of Windows, there's a horizontal > slider for the double-click speed which you can play with.) In > addition, page up/down should increment/decrement the slider in larger > steps, and this works OK. > > 2)In a drop-down list box, left/right arrow keys should do nothing. > > If the keystrokes work OK without a screen-reader, they'll work with a > screen-reader. > > glad to see you're sorting it out, > David. > > On 10/17/07, Martyn Shaw <mar...@go...> wrote: >> OK, I'm on to this one. I have a partial solution to the problem but >> I'm not sure what some keys should do in which situation. >> >> I have working: >> a) left/right arrows in mixer toolbar work OK. >> b) up/down arrow keys work in the project rate box. >> >> What does not work: >> 1) up/down arrow keys in mixer toolbar cause a "Disallowed for some >> reason" ding. >> 2) left/right arrow keys in the project rate box cause a "Disallowed for >> some reason" ding. >> 3) Device Toolbar not yet addressed at all. >> >> I have not checked the changes in yet, but you can get a Release version >> of a zipped win exe at http://mjshaw.at-uclan.com/audacity.zip >> >> So, are a) and b) OK? >> What should happen for 1) and 2), and any other key presses that I >> haven't tested? >> >> I've no idea how this works with a screen reader, but I've >> copy/pasted/modified what Leland did, so maybe it's ok? >> >> Martyn >> >> David Bailes wrote: >>> Hi Gale, >>> >>> On 10/13/07, Gale Andrews <ga...@au...> wrote: >>>> | From "David Bailes" <drb...@go...> >>>> | Sat, 13 Oct 2007 10:05:17 +0100 >>>> | Subject: [Audacity-devel] keyboard interaction bug in 1.3.4rc0.0 >>>> | On 10/13/07, Gale Andrews <ga...@au...> wrote: >>>> | >>>> | > So it seems this makes it very difficult to change input source, >>>> | > input/output >>>> | > levels or Project Rate without a mouse. >>>> | >>>> | It's impossible to change the input and output levels. >>>> >>>> It is not impossible. If you can emulate a double left-click or double >>>> right-click you can change the value in the dialogue box that appears. >>>> And if you tab into one of the level sliders, then left arrow and OK >>>> the warning, you'll see the slider has moved left. If you tab out and >>>> back in you can repeat that step to move the slider further. Or of >>>> course you can change the value in the system mixer, which users with >>>> broken or generic sound card drivers on Windows often have to do anyway. >>>> >>>> | I guess this is priority aim-to for 1.4, and release noted if not >> fixed? >>>> | I think it should be essential. If it isn't fixed before >> 1.4.release, >>>> | then 1.4 will be essentially unusable for users of screen readers. >>>> >>>> It can't strictly be essential as it is not a crashing issue. It is >> marked now as >>>> Priority Aim-to, and marked to be release noted if not fixed. However it >>>> sounds as if Vaughan may be keen to get on the case. >>> You're right, there are work arounds. But if not fixed, it will >>> probabably mean that for screen readers 1.3.3 would be preferable to >>> 1.4.0, which would be a shame. >>> >>> David. >>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Splunk Inc. >>> Still grepping through log files to find problems? Stop. >>> Now Search log events and configuration files using AJAX and a browser. >>> Download your FREE copy of Splunk now >> http://get.splunk.com/ >>> _______________________________________________ >>> Audacity-devel mailing list >>> Aud...@li... >>> https://lists.sourceforge.net/lists/listinfo/audacity-devel >>> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Audacity-devel mailing list >> Aud...@li... >> https://lists.sourceforge.net/lists/listinfo/audacity-devel >> > |