[gmpi] Re: lost-n-found #3 parameter stuff

>On Sat, Nov 06, 2004 at 07:44:29AM -0500, Paul Davis wrote:
>> my understanding of events is that they are processed synchronously
>> with audio processing. that doesn't work for a GUI that wants to show
>> the user a rolling "flow" through a value range. or at the very least,
>> it doesn't work very well at all.
>
>Right.  every GUI param change has a latency to when it is actually
>audible.

we're not talking about *changing a parameter*.

we are talking 100% about a GUI-side change in what is *visible* on
screen (or wherever). the GUI wants to change the displayed value (not
the parameter) as the user drags the mouse, presses a spinbutton,
whaever. the parameter will only be changed at the *end* of the
action. this is not a gesture - its the user moving through a range of
values until they find the right one, with a GUI that for its own
reasons does not wish to set the parameter for every displayed
increment/decrement.. 

>> i think that you can't to do this with events, it has to be done with
>> explicit, synchronous callbacks into the plugin. also, i think this is
>> a massively better design than even the AU model - trying to enumerate
>> all the possibilities for parameters is a battle nobody can win.
>
>You think which is a better design?
>
>The design I suggested for increment takes this into account, by
>explicitly making the caller send an event.  Thus, if the GUI wants to
>send an event for every increment, it can.  If it wants to have a
>rate limit and only send one event per second, it can.
>
>Adding a synchronous way of changing a parameter becomes a locking
>nightmare for every plugin devel.

again, i am not talking about changing a parameter. i am talking about
the GUI knowing what to display during a drag operation (or
similar). we do not want to send events, we want to simply ask the
plugin "what should the next displayed value be if i am incrementing
by a nominal unit?"

--p

----------------------------------------------------------------------
Generalized Music Plugin Interface (GMPI) public discussion list
Participation in this list is contingent upon your abiding by the
following rules:  Please stay on topic.  You are responsible for your own
words.  Please respect your fellow subscribers.  Please do not
redistribute anyone else's words without their permission.

Archive: http://www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe

Other related posts: