Re: AW: AW: [Jsynthlib-devel] Okay... so why can't I edit a patch with this?

[Bill Z. <wrz...@po...>]

Joe Emenaker wrote:

> My primary example of a *missing* window is in the "Get" process. I 
> try to get a patch, and I see a window telling me that this driver 
> doesn't support patch requesting, so I should initiate a dump from the 
> device. And there's an OK button.

Yeah, that whole thing's pretty goofy.  But I think I have an even 
simpler proposal:

If Driver can request a patch, then you get:

Select patch
[Device       ]
[Driver        ]
[Bank         ]
[Patch         ]
[Get]   [Done]

[Paste] is redundant, since if the user clicks [Get], we know they want 
the patch, so we can just toss it into the library.  [Done] just closes 
the window, so [Cancel] is redundant too.

If the Driver can't request a patch, then you get a different diaglog:

Please start manual patch dump.
All dumps will be saved.
[Done]

That's it.  If JSL gets a sysex, it feeds it to a driver, gets the 
patch, and stuffs it into the library.  Again, if the window is open, we 
know the user wants to download patches, so other buttons are 
redundant.  We might want want a Channel Number selector, if there might 
be stray packets flying around the MIDI bus.

There's one question though:  Is the JSL driver set strong enough to 
make this automatic?  Can they create a patch from a random set of 
sysexs?  Or would we need a [Save as Patch] button so the user could 
tell JSL when one complete patch has been sent?

-Bill