On Saturday 10 January 2004 11.03, Steve Harris wrote: [...] > > What you describe sounds to me *exactly* like what we've been > > discussing, except that it appears to be using function calls > > rather than events. (And no IDs, but that's additional > > information, and doesn't really change the logic behind the > > capture/release feature.) > > I think the point is that the plugin has to request reception of > capture/release events from the host. Sounds like a good idea to > me, one less thing to process. Yes. Though, I'd prefer "hint a control as capture/release aware" to "asking the host to send capture/release events", mostly because it's just another property of a control (ie info used when making control out->control in connections), rather than some special plugin/host interaction. (It *could* be in some hosts, but I'd rather not have it designed into the API.) //David Olofson - Programmer, Composer, Open Source Advocate .- Audiality -----------------------------------------------. | Free/Open Source audio engine for games and multimedia. | | MIDI, modular synthesis, real time effects, scripting,... | `-----------------------------------> http://audiality.org -' --- http://olofson.net --- http://www.reologica.se --- ---------------------------------------------------------------------- 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