Re: [Audacity-nyquist] [Audacity-quality] Floating point, input from slider widget

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

> Date: Sat, 28 Aug 2010 06:54:25 +0200
> From: edgar <edg...@we...>
> Subject: Re: [Audacity-nyquist] [Audacity-quality] Floating point
> 	input from slider widget
> <snip>
> 
>  > Of course, other Nyquist interpreters won't have this, so some plugins
>  > that work in Audacity won't work in others. I'll remove it if people
>  > think it's a bad idea.
> 
> The 'control' lines do not exist in any other Nyquist interpreter,
> the parsing of "int", "real" and "float" only happens with Audacity.

Thanks. Wasn't sure about that.


> 
> Also the sound-file i/o with Nyquist in Audacity is heavily incompatible
> to all other Nyquist interpreters (what still is the main source of all
> problems with Nyquist in Audacity), so most Nyquist plugins will not work
> with CMU Nyquist anyway (there is only one other Nyquist interpreter).

Likewise, thanks, wasn't sure about that.


> 
>  >> Ignoring the control would be consistent with how Audacity treats other
>  >> malformed controls, though a debug message would certainly be more
>  >> helpful. Would it be possible to send a message to the debug window just
>  >> to say that a control has been ignored?
>  >>
>  >> Unfortunately, the place it can be detected is at startup, when all the
>  >> Nyquist plugins are loaded, in a method that parses a single line. The
>  >> debug window is used when the plugin is invoked, in a far distant piece
>  >> of code.
> 
>  > * If it's not "real", "float", or "int" it fails to create the control.
>  > It puts up a warning alert box. This all occurs before the Audacity Log
>  > window is created, so it does not go to the log...
> 
> Sounds to me like a workaround, but is far better than ignoring the bug.

Actually, not a workaround. Because the Nyquist plugins are parsed at
startup (so they need not be parsed every invocation), that's where the
error can be detected, not on invocation.

Was asking whether people prefer alert dialog (as for some other Nyquist
errors that get caught) or the log (without alert dialog).



> 
>  > That raises the general question of whether to create the log window
>  > earlier, so the message goes to the log, but then does *not* bring up
>  > an alert box. Comments?
> 
> It that's no huge code surgery this is the far better solution. I think
> an alert box is OK for developers, but probably will annoy the casual
> user, who just simply expects a plugin to work.

Well, we should always QA any plugin we're supplying with Audacity
before releasing it, certainly to the point of parsing it once. So users
should not see these, and the developer will get a prominent alert
rather than it being just treated as int without notification.

Thanks!

- Vaughan