From: Joe E. <jo...@em...> - 2005-05-14 08:05:44
|
Joe Emenaker wrote: > ... the SysexGetDialog class regularly polls the queue and, > apparently, steals the messages out of the queue to put in its *own* > queue. This other queue, in SysexGetDialog doesn't appear to be > accessible to the Driver subclasses. > > The reason for this *seems* to be so that the SysexGetDialog can show > a running count of the bytes received. However, there's no reason it > can't do this while leaving the messages in the original queue. I think I'm going to investigate implementing a "listener" system with the midi input queues.... where various parts of the program add themselves as "listeners" to be notified when a message comes in. Seems like a better way than to have SysexGetDialog running a timer to poll the inport. Also, what does everyone else think about JSL being able to receive a patch even when the SysexGetDialog isn't open? For example, if JSL is just sitting there, and you dump a patch from a synth, it could pop up a message saying "JSL just received a patch dump which looks like a Alesis DM5 Bank. Would you like to save it in your current library or discard it?". Then, all the SysexGetDialog class would need to do is arrange to send out dump requests (and notify the receiving mechanism that a certain type of patch is expected). - Joe |