Bug 2608 – Audacity reacts to shift key when it is not the front application

••• Introduction •••
••• Keywords •••

Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla

Bug 2608 - Audacity reacts to shift key when it is not the front application


Summary:	Audacity reacts to shift key when it is not the front application

Status:	RESOLVED FIXED

Product:	Audacity
Classification:	Unclassified
Component:	Application Core
Version:	3.0.0
Hardware:	All All

Importance:	P3 RepeatableAll
Assigned To:	Default Assignee for New Bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2020-12-05 14:21 UTC by Bill Wharrie
Modified:	2021-01-02 09:26 UTC (History)
CC List:	7 users (show)

See Also:
Steps To Reproduce:	Tested on macOS 10.15.7 1) Start Audacity 2.3.3 or any later version (up to and including 3.0.0 a675b59) 2) Switch to or start TextEdit (or any other program) 3) Move the TextEdit window so you can see the Transport Toolbar in Audacity 4) Hold down the shift key 5) The play and record buttons respond to the shift key by changing their icons
Release Note:
First Git SHA:
Group:	---
Workaround:
Closed:	2021-01-02 00:00:00

Flags:	petersampsonaudacity: Regression+ petersampsonaudacity: Test‑OK‑Win+ petersampsonaudacity: Test‑OK‑Mac+ stevethefiddle: Test‑OK‑Lin+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Bill Wharrie 2020-12-05 14:21:18 UTC

Does not occur in 2.3.2 or earlier.
Steve reports this also happens on Linux.

Comment 1 Peter Sampson 2020-12-06 04:58:29 UTC

I confirm this also happens on W10 with 2.4.2 and latest 3.0.0 alpha.

I also confirm that it's a regression on 2.3.2

Comment 2 Peter Sampson 2020-12-06 05:36:53 UTC

Tested on W10 and macOS 11.0.1 with Audacity 3.0.0 0bd21e1

This now works properly on Win and Mac - when the Audacity is not the active Window it no longer intercepts the Shift key used in the active window

Comment 3 Paul L 2020-12-06 13:32:33 UTC

The fix was at 0bd21e171c1b25d53f7cf611520a417bb1ae58bc

Comment 4 Steve Daulton 2021-01-02 09:26:42 UTC

Now tested on all platforms.
Resolved.