Audacity Bug Summary
••• Introduction •••
••• Keywords •••
    Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla



Bug 1553 - "Remove focused track" shortcut does not respect Do on Pause.
"Remove focused track" shortcut does not respect Do on Pause.
Status: RESOLVED WORKSFORME
Product: Audacity
Classification: Unclassified
Component: Audio IO
2.1.3
Per OS All
: P4 RepeatableAll
Assigned To: Default Assignee for New Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-12-01 18:28 UTC by Gale Andrews
Modified: 2018-08-20 11:45 UTC (History)
4 users (show)

See Also:
Steps To Reproduce:
1 Pause playback or recording and use the default SHIFT + C shortcut to close the focused track. 2 Expected with new "Do on Pause" behaviour: playback stops and the focused track is removed. Actual: A system "ding" is heard and transport continues.
Release Note:
First Git SHA:
Group: ---
Workaround:
Closed: 2018-08-20 00:00:00
petersampsonaudacity: Test‑OK‑Mac+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gale Andrews 2016-12-01 18:28:01 UTC

    
Comment 1 Peter Sampson 2018-03-18 07:12:05 UTC
Following commit https://github.com/audacity/audacity/commit/a47df37ea493c034dc01fe19e0fb5a3cb735accc for this bug I tried testing this.

On Mac mac)S 10.13.3 I have the latest 18Mar18 nightly and this now works correctly with the focused audio track removed as expected (but note that you have to turn on the Full set of keyboard shortcuts.



I cannot test yet on Windows as the latest nightly build failed - but I am very confused as when I tun on Full shortcuts and look at Shift+C and that seems to be assigned to Extra Menu > Mixer > Decrease Recording Volume
Comment 2 James Crook 2018-03-18 07:29:23 UTC
The fix was to bug 1533 :-)
Comment 3 Peter Sampson 2018-03-18 07:38:20 UTC
OOPS yes <blushes deeply>

BUT - this bug now appears to work on Mac - AND we still seem to have different commands assigned for Shift+C in Mac and Windows :-//
Comment 4 James Crook 2018-03-24 11:27:52 UTC
Tested and works for me (on windows).
Probably flags for commands were updated at some stage.

The shortuct assignment reported in comment #3 is not part of this bug.