[gmpi] 3.11 topic: Spontaneous parameter changes
- From: Tim Hockin <thockin@xxxxxxxxxx>
- To: GMPI list <gmpi@xxxxxxxxxxxxx>
- Date: Sun, 4 Apr 2004 23:47:34 -0700
It was asked how to support plugin-originate parameter changes. This was
expanded to include parameters which may not accept a value, even though it
is technically in-bounds.
The use cases given were:_
- two parameters knobs which are offset but locked. The maximum value of
the smaller of the two is (max - offset).
- plugin-based patch morphing. Many plugins are doing this today. The
knobs move spontaneously in the GUI based on some morphing rules.
The requirements do suggest a listener model, which alleviates a lot of this
problem. The plugin alerts the listeners that a parameter is changing.
This means that all GUIs attach a listener to the controlled parameters.
While this makes for good MVC seperation, it might be too much overhead.
It was proposed that controllers can assume that an in-bounds value will be
accepted. Parameters which might change spontaneously or which might
reject some in-bound values should be flagged. GUIs can see set up
listeners for only the parameters which might need them. All other
parameters can be assumed to succeed for in-bound values.
Q: What does the requirements doc need to say about this?
----------------------------------------------------------------------
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: //www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
Other related posts:
