From: Jeff W. <jww...@ya...> - 2005-03-02 19:29:05
|
I have a couple of suggestions making SysexWidgets a little more flexible. I have often times run into a situation where the range of values sent by a ScrollBarWidget or a KnobWidget needs to go from high to low rather than from low to high. I wanted to see what would happen if I created a KnobWidget with the min and max values switched around (i.e. min = 127 and max = 0) so I tried it. The SysexSender already appears to handle this correctly but the ParamModel just sets the value to zero for all input values. The way I have handled this in the past was to subclass ParamModel to handle the high to low range. How much effort would it take to modify ParamModel to handle this situation and make subclassing unnecessary? Another issue I ran into happened when I attempted to create a CheckBoxWidget to control the Drive setting on the V-Amp 2. This is just an on/off setting and a CheckBoxWidget would be the obvious choice. Apparently the CheckBoxWidget is hard wired to send only values of 0 for "off" or 1 for "on". But the Drive setting on the V-Amp is turned off by any values in the range 0-63 and on by any values in the range 64-127. Both a 0 and a 1 will turn it off. To use a CheckBoxWidget for this right now, I would need to subclass both a ParamModel and a SysexSender. But if the CheckBoxWidget had another constructor that accepted custom on and off values, this would not be necessary. __________________________________ Celebrate Yahoo!'s 10th Birthday! Yahoo! Netrospective: 100 Moments of the Web http://birthday.yahoo.com/netrospective/ |