Yeah, this is pretty good, I like it better than any kind of
one-source-per-target rule.
-- Chris G.
Tim said:
Any host which allow multiple event sources for one target needs to handle this. By handle this, I mean one of two things:
1) Do nothing. Send all events to the plugin. The vast majority of plugins do not care about gesture-start and gesture-end, and will ignore them. If two sources fight, you will get a knob that bebops around. Plugins don't need to handle anything special, and ignore things they don't need.
2) Act as a priority-based switch. Based on the source of inputs, decide which events make it to the plugin, and which get dropped. Plugins don't need to handle anything special, and ignore things they don't need.
Both solutions are perfectly acceptable, and are NOT mutually exclusive. It is the sort of feature that, if well implemented, can differentiate hosts.
Forcing the plugin to sort based on source ID is probably not the cleanest answer (do you really want each plugin deciding which input has higher priority? do you really want each plugin handling priority setting? Yuck.)
---------------------------------------------------------------------- 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
