Ok the issue is simply due to how the decimals property works: the fader doesn't notify value changes that don't exceed its decimals settings, but the matrix widget still gets the un-rounded value (on purpose). Increasing decimals is enough to fix it (3 works fine here).
There's currently no plan to add value interpolation to any widget.
oouch, pity , that would be hugely useful for the big matrices with faders, for me at least 
I guess I can can try doing something with canvas instead.
Cheers
Hi there, I've found this , not sure if this is a bug, but using this function with a range object works fine send("myoscrange", ...value) I got the osc message formatted like I need.
However if I try the same function with a matrix (with a single range child) the osc message is formatted differently. As you can see here, it adds brackets:
Is there any special reason why this behaves like that, or am I missing something?
Thanks in advance
btw - using latest OSC version (1.21)
OK I see, figured this out, send("/myOscRange", ...value[0]) returns the two values for the first range object in the matrix.
1 Like