This way you’ll be able to send the interger value to /text/address/int [preArgs] (without the leading slash, the listener’s address is considered relative to the host widget’s).
Note that 128 is 0x80, if you need to display 0x7F you’ll have to decremenent intValue by 1.
Nice!
OK, thank you, I didn’t know this about OSC{} listeners and preArgs.
For now I am using a matrix, so I can send /REG 1 127 or /REG 2 0 to update the faders.
Is it still possible to use OSC() in this case?
Yeah you’re right about 127 vs 128, I was tired
I think the new JS syntax will be really useful for formatting or quick calculations.
And I have seen that the set() function is available here too, this will be really useful too.
I still not really understand when this code is triggered.
In my case, sending OSC to the widget triggers it, but if I use for instance the value of another widget as input (like @{widget1}), will this code be triggered each time widget1 value changes?
In my case, sending OSC to the widget triggers it, but if I use for instance the value of another widget as input (like @{widget1}), will this code be triggered each time widget1 value changes?