On 20/09/2011 20:42, William Zwicky wrote: > On Tue, Sep 20, 2011 at 10:45 AM, Frankie Fisher < > [email protected]> wrote: > >> .. constant re-querying is a pain in the arse .. >> > How about this: jsl only saves a list of which ports were DISabled, by > name. (There's a unique name string for each port, isn't there?) I think > this supports the use cases mentioned above -- jsl picks up all ports with > about spamming user, but hides the ports the user doesn't want jsl to > manage. This would probably work as long as we also have some method of automatically figuring out which port a device is on or if its not connected. would we need to do a device scan (06 01) each time at startup to work out which port a device is on? I know not all devices support this though. > > I also believe that jsl should be port-agnostic -- if a synth moves to > another port, jsl should assume it's the same synth and not bother the > user. But there's another problem (maybe) -- what if the user has two > copies of the same synth? Is that even a problem? Can we assume that duplicate synths will always have a different device id? or are there some devices where this isn't the case? maybe synths that dont support device ids?
frankie ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Jsynthlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
