From: Joe E. <jo...@em...> - 2005-05-07 08:36:30
|
Joe Emenaker wrote: >If we had >several different implementations of PatchNameModel like: > > FixedLengthPatchNameModel(int patchNameStart, patchNameSize); > TerminatedPatchNameModel(int patchNameStart, byte terminator); > >Then it could make it easier to accomodate other name-storage methods. > > I just thought of another one. For some time, I've felt that it would be nice to be able to give names to patches which, in the hardware device itself, doesn't have a name. The Behringer FCB1010 is an example; it has no display on it and the patch format doesn't support names. However, what if there was something like: HashValueNameModel(Preferences pref); The idea is that, when the user triggered a "setPatchName", the HashValueNameModel would calculate the hashvalue of the patch data and store the name in a preferences file (probably the one that JSL gave to the driver when it was instantiated)... and could also look them up from getPatchName. - Joe |