> So the host has to call this method for every frame for which there exists > an event? And the host then needs to interpret and propogate the returned > list of events and propogate that back to all controllers. ick. > > If we want to explore that route, how about a 1-call per event target per > timeslice method. The problem that I see with that is that the plugin needs to be rendering in order to get any events. What if rendering is currently stopped, but the user for example triggers a change-preset event? Then the event doesn't really get passed (and therefore listeners like GUI elements don't get updated) until rendering begins again. This can cause unwanted unresponsiveness for some types of events. At least that's how it seems to me, but I might be missing something with this approach... Marc ---------------------------------------------------------------------- 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