Hello !
I wanted to use a few switches to navigate through one single panel's tabs.
I did it settings values [1,2] for the first switch, [3,4] for the second one, and [5,6] for the last one.
Then, i created three variables, V1, V2, V3 to get the values of the switches.
And a fourth variable, V_Tab, with #{(@{V1}+@{V2}+@{V3})-1} as value. The one variable to switch tabs.
And this kind of line to turn off unused switches :
So, two questions... it works as i want, everything's ok... but :
is there any way to make it shorter in terms of script and settings ?... Because i'll need more than three switches...
i tried without variables as V1,V2,V3, but only one V_Tab getting #{(@{S1}+@{S2}+@{S3})-1} where S1, S2, S3 were the switches Ids. But it did'nt work. And i don't understand why...
is there any way to make it shorter in terms of script and settings ?... Because i'll need more than three switches...
You can get a grid layout with only one switch, so that would simplify it. No need for variables or anything here, linkId does the job: switches.json (9.3 KB)
En mettant send sur 127.0.0.1:7777 et osc-port sur 7777 tu diriges tous les messages envoyés par OSC vers lui-même et ça génère un conflit car les switches et le panel envoient chancun des messages osc. Tu peux empêcher le problème en mettant bypass sur true sur les switches.
When interacted with, widgets with at least one target (including the server's defaults) send osc messages of the following form:
préciser que c'est dans le champ Send qu'on indique les targets externes par défaut pour toutes les widgets
When interacted with, widgets with at least one target (including the server's defaults set into the Send field) send osc messages of the following form:
Ce sont évidemment des suggestions que tu sauras ignorées fort justement
Merci pour ton aide et encore désolé pour le dérangement.