Bug 2216 – Mac: Cannot use Enter to effect an Effect after entering numeric data in a field

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

Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla

Bug 2216 - Mac: Cannot use Enter to effect an Effect after entering numeric data in a field


Summary:	Mac: Cannot use Enter to effect an Effect after entering numeric data in a field

Status:	RESOLVED FIXED

Product:	Audacity
Classification:	Unclassified
Component:	Application Core
Version:	2.3.2
Hardware:	Mac macOS

Importance:	P1 Repeatable
Assigned To:	Default Assignee for New Bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2019-09-23 07:37 UTC by Peter Sampson
Modified:	2019-09-23 09:12 UTC (History)
CC List:	7 users (show)

See Also:	2107
Steps To Reproduce:	1) get some audio 2) make a selection 3) Effect > Amplify (or other effect with numeric entry field(s) ) 4) type -10 in New Peak Amplitude (or other numeric field) 5) Click Enter 6) Observe nothing happens Expected behavior: the effect is acted upon
Release Note:
First Git SHA:
Group:	---
Workaround:
Closed:	2019-09-23 00:00:00

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

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 Peter Sampson 2019-09-23 07:37:45 UTC

On Mac when using effects with  numeric entry fields, if you use the field(s) to enter data you then cannot use Enter to make the effect work.

In contrast just calling the effect up and then pressing Enter will cause the effect to work.

This was caught and reported recently by a Forum poster:
https://forum.audacityteam.org/viewtopic.php?f=47&t=106831&p=377263

Testing shows that this was introduced in 2.2.0 - and is a regression on 2.1.3 - hence the P1.

This bug is still present on 2.3.2 (as reported by the Forum poster) verified by testing.   But testing on 2.3.3 alpha jc008 shows the this bug has been "fixed" presumably by other maintenance changes that we made for 2.3.3 - accordingly it willmarked as RESOLVED FIXED - but logged here for tracking purposes.

Comment 1 Peter Sampson 2019-09-23 07:38:28 UTC

Does not occur on W10