Re: [Audacity-quality] Numerical input validation

[Vaughan J. <va...@au...>]

On 11/26/2013 1:15 AM, Gale Andrews wrote:
>
> | From Vaughan Johnson <va...@au...>
> | Mon, 25 Nov 2013 11:36:03 -0800
> | Subject: [Audacity-quality] Numerical input validation
>> On 11/25/2013 1:39 AM, Gale Andrews wrote:
>>>
>>> | From Vaughan Johnson <va...@au...>
>>> | Sun, 24 Nov 2013 19:06:51 -0800
>>> | Subject: [Audacity-quality] Numerical input validation
>>>> On 11/23/2013 7:48 PM, Steve the Fiddle wrote:
>>>>> On 24 November 2013 02:47, Vaughan Johnson <va...@au...> wrote:
>>>>>> On 11/23/2013 9:19 AM, David Bailes wrote:
>>>>>>> On Fri, Nov 22, 2013 at 3:02 PM, Steve the Fiddle
>>>>>>> <ste...@gm... <mailto:ste...@gm...>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>        The main problem that we have with using the new validator is that
>>>>>>>        wxFloatingPointValidator limits the precision to a specified number of
>>>>>>>        decimal places.
>>>>>>
>>>>>> I don't think so. There are two constructors for the
>>>>>> wxFloatingPointValidator class. See valnum.h.
>>>>>>
>>>>>> One of them specifies limited precision, per comment "// Ctor specifying
>>>>>> an explicit precision."
>>>>>>
>>>>>> The other says "// Ctor using implicit (maximal) precision for this
>>>>>> type." So maybe the wrong choice of constructor was made in Nyquist.cpp,
>>>>>> but it should be an easy fix. And I'm +1 on using maximal precision for
>>>>>> the global change.
>>>>>
>>>>> I have already tried that. It works, but then the number is displayed
>>>>> with 15 decimal places, which is not really what we want
>>>>
>>>> So there's a little conflict here, between being able to enter very high
>>>> precision and being able to see what's been entered without scrolling
>>>> the text.
>>>>
>>>> Along the lines of what David asked, can we decide on a sufficiently
>>>> high precision for each effect? And if some need maximal precision, live
>>>> with the current display issue, until we override that behavior? Better
>>>> than what we currently have.
>>> [...]
>>>>>>> For some Nyquist plug-ins (such as "Tempo" in Click
>>>>>>>        Track) this is clearly a regression (bug 685).
>>>>>>
>>>>>> Okay, thanks. I think this can be fixed by using the other constructor.
>>>>>
>>>>> As above, we don't really want the default tempo displayed as
>>>>> 120.000000000000000.
>>>>
>>>> So are you against the width of the control, or the integer values,
>>>> where it shows all those unnecessary zeroes? On non-integer values, for
>>>> high precision, shouldn't it show the actual precision?
>>>
>>> +1 in principle to it showing the actual precision for non-integer
>>> values.
>>>
>>> But I am guessing that if the default tempo was 120.000000000000000
>>
>> There's no "default tempo".
>
> By "default tempo" I mean the value you see for "Tempo [beats per
> minute]" in Click Track when you first open it in an Audacity session.

It's blank when I open it with reset prefs. So I'm guessing that 'first 
open' is actually not 'first'.


>
>
>>> and you tabbed into that, the selected text would only show
>>> "0000000" give or take a digit because the selection would auto
>>> scroll to the end.
>>
>> ? Clearly, we'd need to make the control wider.
>
> Fine, if we can.

Of course we can, it's software.

- V


>
>
>
> Gale
>
>
>>> If that's a concern (I think it is) then we can't show more than six
>>> or seven numbers plus the decimal separator somewhere amongst
>>> them for the default value.
>>>
>>>
>>>
>>>
>>> Gale
>>>
>>>
>>>> Since we're using a backport of the wxWidgets valnum.c, we can just fix
>>>> it, I expect. Probably just a matter of a change of one or two
>>>> formatting specs.
>>>>
>>>>
>>>> - V
>>>>
>>>>
>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Just out of curiosity, why would someone need to specify the number of
>>>>>>> beats per min to more than two decimal places? If they do need to do
>>>>>>> this, how many decimal places would they need?
>>>>>>
>>>>>> Right. So for some cases, we might want to specify the precision, and
>>>>>> choose the other wxFloatingPointValidator constructor.
>>>>>>
>>>>>> The point is that these new validators are much better than previously
>>>>>> available. And they can be overridden, to provide specific functionality
>>>>>> we want.
>>>>>
>>>>> Yes, they are clearly much better, but how do we then restrict the
>>>>> number of zeros shown?
>>>>>
>>>>> Steve
>>>>>
>>>>>
>>>>>>
>>>>>> - V
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Shape the Mobile Experience: Free Subscription
>>>>> Software experts and developers: Be at the forefront of tech innovation.
>>>>> Intel(R) Software Adrenaline delivers strategic insight and game-changing
>>>>> conversations that shape the rapidly evolving mobile landscape. Sign up now.
>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
>>>>> _______________________________________________
>>>>> Audacity-quality mailing list
>>>>> Aud...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Shape the Mobile Experience: Free Subscription
>>>> Software experts and developers: Be at the forefront of tech innovation.
>>>> Intel(R) Software Adrenaline delivers strategic insight and game-changing
>>>> conversations that shape the rapidly evolving mobile landscape. Sign up now.
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> Audacity-quality mailing list
>>>> Aud...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Shape the Mobile Experience: Free Subscription
>>> Software experts and developers: Be at the forefront of tech innovation.
>>> Intel(R) Software Adrenaline delivers strategic insight and game-changing
>>> conversations that shape the rapidly evolving mobile landscape. Sign up now.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Audacity-quality mailing list
>>> Aud...@li...
>>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>>
>>
>> ------------------------------------------------------------------------------
>> Shape the Mobile Experience: Free Subscription
>> Software experts and developers: Be at the forefront of tech innovation.
>> Intel(R) Software Adrenaline delivers strategic insight and game-changing
>> conversations that shape the rapidly evolving mobile landscape. Sign up now.
>> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Audacity-quality mailing list
>> Aud...@li...
>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>
>
>
> ------------------------------------------------------------------------------
> Shape the Mobile Experience: Free Subscription
> Software experts and developers: Be at the forefront of tech innovation.
> Intel(R) Software Adrenaline delivers strategic insight and game-changing
> conversations that shape the rapidly evolving mobile landscape. Sign up now.
> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
> _______________________________________________
> Audacity-quality mailing list
> Aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>