Bug 685 – Limited precision for Nyquist plug-in sliders

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

Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla

Bug 685 - Limited precision for Nyquist plug-in sliders


Summary:	Limited precision for Nyquist plug-in sliders

Status:	CLOSED DUPLICATE of bug 681

Product:	Audacity
Classification:	Unclassified
Component:	Built-in FX
Version:	2.0.6
Hardware:	PC All

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-11-15 07:16 UTC by Steve Daulton
Modified:	2018-08-20 11:45 UTC (History)
CC List:	5 users (show)

See Also:
Steps To Reproduce:
Release Note:
First Git SHA:
Group:	---
Workaround:
Closed:	2018-08-20 00:00:00

Flags:	stevethefiddle: Regression+

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 Steve Daulton 2013-11-15 07:16:55 UTC

Prior to the validator upgrade, values could be typed into the text box of a slider widget with "unlimited" precision (around 15 decimal places).
The precision is now limited to a fixed number of decimal places (currently 2).

For some plug-ins (such as the "Beats per minute" control in "Click Track") this loss of precision is a significant (probably P3) regression.

Comment 1 Gale Andrews 2013-11-16 22:35:30 UTC

Just adding some text from correspondence with Steve, at least for my benefit. 

The number of decimal places is a required part of the new validation. 

Steve wrote:
> What we would need to do is to rewrite NyquistDialog so that the number text can
> be intercepted after validation and formatted to show the number of decimal places 
> required by the value. There was no need for this additional code before the validator 
> upgrade, so it does not currently exist.

Comment 2 Vaughan Johnson 2013-11-23 22:04:47 UTC

(In reply to comment #1)

>The number of decimal places is a required part of the new validation. 

Not necessarily true. See my post on audacity-quality "Numerical input validation" thread. We can use the other wxFloatingPointValidator constructor.

Comment 3 Steve Daulton 2013-12-23 10:08:14 UTC

Bug 681, bug 685 and bug 699 are all caused by r12723 "Backported
wxWidgets-3.0rc1 number validators"

*** This bug has been marked as a duplicate of bug 681 ***