Maybe what we need to do for 2.0.4 is to withdraw the
current shortcuts for Go To Selection Start/End of
Ctrl+4 and Ctrl+5 - leaving them with no assigned
This way we could delay concluding the discussion as to
what their shortcuts properly should be until after 2.0.4 is
released, giving us more time to consider this more fully
without forcing ourselves into a corner.
Tel: +44 (0)1625 524 780
Mob: +44 (0)7732 278 299
From: Gale Andrews <gale@...>
Sent: Monday, August 26, 2013 7:33 PM
Subject: Re: [Audacity-devel] Confirmed shortcuts for 2.0.4 ?
| From Vaughan Johnson <vaughan@...>
| Sat, 24 Aug 2013 19:16:42 -0700
| Subject: [Audacity-devel] Confirmed shortcuts for 2.0.4 ?
> On 8/24/2013 4:04 PM, Gale Andrews wrote:
> > | From David Bailes <drbailes@...>
> > | Sat, 24 Aug 2013 20:31:13 +0100
> > | Subject: [Audacity-devel] Confirmed shortcuts for 2.0.4 ?
> >> On Sat, Aug 24, 2013 at 7:32 PM, Gale Andrews <gale@...> wrote:
> >>> Vaughan,
> >>> I have mentioned the need to decide on this before now.
> Okay, but per David's response, it was not actually agreed. I wrote,
> "This discussion does not seem to have reached a clear consensus."
> Another tracking issue, I think. When almost-consensus was reached, 3rd
> yea, might have been good for it to become an agenda item (and bugzilla
> is our current agenda tracker).
The problem was that the "change the Go to Selection shortcuts"
discussion mutated to another patch to change the zoom shortcuts
so they were like "browser zoom".
Then that patch stalled because it broke the current zoom shortcuts.
I think the consensus was to go ahead with that patch but to keep
the current zoom shortcuts as second zoom shortcuts (at least for
a time). We don't have a patch that does that yet (and I think
there were a few other improvement suggestions to be considered).
> and bugzilla is our current agenda tracker
That was a very recent decision I think.
Is it just at release time that we want to create a bugzilla item
in order to load a patch that can be marked "ready"?
> >>> The fact that it's frustrating for users if shortcuts change is the
> >>> very reason I raised it. View > Go To Selection Start and View >
> >>> Go To Selection End are new to 2.0.4, so the time to get the
> >>> shortcuts right is in 2.0.4 release.
> >>> I think the consensus is there e.g. Steve
> >>> http://audacity.238276.n2.nabble.com/Introduction-and-Go-to-Selection-patch-td7557726.html#a7558037
> >>> seconded by me and thirded by Martyn:
> >>> http://audacity.238276.n2.nabble.com/Introduction-and-Go-to-Selection-patch-td7557726.html#a7558056.
> Should probably have just happened then, and dealt with the
> accessibility issues afterward.
> So please point to which patch(es) in that thread are approved by
> QA for 2.0.4. Will apply them. Thanks.
We don't have a patch for Go to Selection shortcuts on their own
due to the reason above, so I've attached mine.
* "menus_one_pair_for_go_to_selection.patch" changes the
"Go to Selection Start" shortcut to CTRL + [ and that for "Go
to Selection End" to CTRL + ] . It also groups the "Zoom",
"Fit" and "Go" items in the View menu on which there was
* "menus_two_pairs_for_go_to_selection.patch" does the same,
plus it adds second shortcuts CTRL + SHIFT + G for "Go to
Selection Start" and CTRL + SHIFT + H for "Go to Selection
End". The second shortcuts can be seen in Keyboard Prefs.
This leaves CTRL + G and CTRL + H free for a possible "Zoom
to Selection Start" and "Zoom to Selection End" command
I've tested both patches on Windows. I marginally prefer not
using up second shortcuts because the minority of people who
can't use the shortcuts with brackets probably can't discover
them without reading the Manual or opening Prefs.
> >>> And I definitely thought you liked them when discussed on
> >>> -quality.
> >>> I don't think David is against them but his view is important.
> >> The only issue which I raised was that shortcuts involving the [ and ] keys
> >> won't work using audacity's default keyboard binding settings on non
> >> uk/us/irish keyboards.
> > Thanks, David. Yes I recall now. Although we already use [ and ]
> > you asked whether we should add another pair of shortcuts that
> > use those brackets.
> > We have CTRL + G and CTRL + H available, which follow on
> > from the existing CTRL + E and CTRL + F in View Menu. After I
> > suggested that, Steve counter-suggested CTRL + [ and CTRL + ].
> > Options:
> > 1 Leave as is at CTRL + 4 and CTRL + 5 (this gives a strong
> > suggestion to me that these are zoom shortcuts which they
> > are not. Probably the least discoverable of the options).
> > 2 CTRL + G and CTRL + H (somewhat less correlation with zoom)
> > 3 CTRL + [ and CTRL + ]
> > 4 Allow both CTRL + G plus CTRL + H and CTRL + [ plus CTRL + ]
> > (but the latter pair is default).
> > I'd still vote for 3. Perhaps find some longer term solution like
> > localized keyboard xml files (optional for user) or force the
> > shortcuts to change with the locale (not sure the latter is a
> > good idea though).
> Should any of the posted patches be applied, regardless of this open
I think yes, because surely we are not going to withdraw the
popular [ and ] default shortcuts at this stage, and I would
imagine the majority of users have keyboards where shortcuts
containing brackets will work.
Whatever solution we devise for localised keyboards can then
apply to [ and ] , CTRL + [ and CTRL + ] and any other default
shortcuts that are affected.
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
audacity-devel mailing list