On Thu, Aug 21, 2003 at 06:11:39PM -0700, Marc Poirier wrote: > Shall we start where we left off with this during the early more free-form > part of the 8 discussions? There was a lot of thorough discussion about > this topic during that time. I still like the idea of saving all > parameter values plus optional blobs, maybe only 1 blob or maybe the > possibility of more, and maybe the blobs themselves are parameters. So, as I kinda described in 8.1 (wrongly, final Summary should be cleared up): I agree blobs are necessary. I don't like blob parameters, because I feel that all parameters should be automatable. This is where I invented stata. Stata are the save/restore hooks. The values of all the stata are the plugin's state. At startup (say, loading a preset), you load all the state data into the plugin's stata. At runtime, you manipulate the parameters. At save time, you read all the stata. It should be trivial to make a single stata for each parameter. This should be the 'normal' case. Slightly odd plugins can add one or more extra stata (which could be int, float, blob, etc) to expose extra state without making an automatable parameter. Plugin's that want to use a single state chunk can even make just one stata, a blob, for their whole plugin. Everybody wins. -- Notice that as computers are becoming easier and easier to use, suddenly there's a big market for "Dummies" books. Cause and effect, or merely an ironic juxtaposition of unrelated facts? ---------------------------------------------------------------------- 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