Quote:
Originally Posted by Funkybot
Why shouldn't this be allowed:
Code:
Widget RotaryD
Encoder b0 19 7f [ > 41 43 45 47 49 < 3f 3e 3d 3c 3b ]
WidgetEnd
Combined with...
Code:
RotaryD FXParam "11" "Mode" [ (10) 0.0 0.5 1.0 ]
???
I'm thinking the widget defines the capabilities (this is an encoder with no acceleration, this is an encoder with an acceleration range, this is an encoder with acceleration values) but the action should actually dictate what CSI does with the encoder. So in the above example, step through those values for every 10 encoder clicks (ignores acceleration - knows to do this based on action syntax). It shouldn't care what type of underlying encoder it is just "move to next step up after 10 positive clicks, or next step down after 10 decrements." |
Yup, you're making the same basic decoupling argument just made in the previous post (cross post
)