On 9/8/2011 8:13 AM, frankster wrote: > What about if the midi layer will never queue more than 1 message from > a particular widget (so the midi layer would have to track the source > of each message) and if multiple messages appeared from the same > widget's Sender class, it would discard all but the most recent.
This strikes me as a great way to do it. We could even do it without the widget losing its place in the queue. We could just replace the old message with the new one. I'm not troubled by the fact that the midi layer would need to track the source. That seems like we could do some handy things with that kind of info down the road. > This would mean that widget messages have to be stateless and > interchangeable. Is this a reasonable condition? It is on the > synths/drivers i've played with but I can't speak for most of them. We could let each synthdriver decide their own queue policy (ie, only hold one message per widget, or hold all of them). A more-complicated solution would be for widgets to indicate which messages belong as a set... but I don't see a need for that. - Joe ------------------------------------------------------------------------------ Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ _______________________________________________ Jsynthlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
