Re: [Jsynthlib-devel] [Jsynthlib-cvs] SF.net SVN: jsynthlib:[1158] trunk/JSynthLib/core

[Frankie F. <jsy...@te...>]

On 20/09/2011 15:13, Joe Emenaker wrote:
>
> I think the toughest part is deciding how JSL should respond when *some* 
> of the selected interfaces go missing. Suppose I have two USB MIDI 
> interfaces, and I have some drivers using ports on each one. Then, I 
> remove one of the MIDI interfaces and then run JSL again. Should JSL 
> re-query the user about:
>   1 - Which ports to listen on?
>   2 - The port assignments for every driver which had its port go missing?
> or do we want to just have JSL fail-over to a default port?
>
> If we just give the user a default, what do we do if that interface 
> shows back up again, later?
Yep this is a problem that came up when I fixed the issue with midi
ports last night. If you have a synth connected to USB interface X which
is disconnected, before it would either end up on a random interface or
crash, whereas now it will fail to load that interface and instead
connect to whichever interface happens to be in position 0. I think this
then gets saved at some point so if you start it up again but this time
the interface is there, you will remain on whichever interface was at 0
the previous time.

I think rather than fall back to a default port the better outcome would
be that it retains the interface the user set it at and the interface
could be marked as unavailable in any lists that are displayed. 
Possibly re-query the user or maybe just warn them that the port is not
available. It would depend if its a common use case to disconnect and
reconnect ports, and if constant re-querying is a pain in the arse or not!

frankie