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

You are all completely missing Mike Berry's point.

Most GUI's will not contact the plugin when "dragging" or "spinning" a
widget's displayed value. It is just generally inefficient to do, and
can cause unintended effects for the output of the plugin.

When dragging, lets say a pitch parameter, the GUI needs to know how
to represent each successive step of the "drag" or "spin" or
"increment" *all by itself*.

None of what is being described usefully addresses this case. Either
find a solution for this, or add a requirement that GMPI host-provided
GUIs must follow strict MVC principles.

--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: