linking radio of switches in different interfaces

[felusch]

Hi all,

I´m a complete newbie ...so please be patient, just bought it today

Is it possible to link the radio funktion on muliple rows of switches on different interfaces?
-> maybe with a script?, any ideas?

thanks for your help
cheers
Bodo

[Phil999]

between interfaces I'm not sure, but between containers or container tabs you can create aliases.

[felusch]

how does it work with aliases? -> there is no match in seraching the manual

[Phil999]

that is true - strange. Anyway, in the editor, you can right-click on an object, and choose 'Create Alias'.

[bxsj]

how does it work with aliases? -> there is no match in seraching the manual

Creating an alias of an object basically creates a "clone". That is, both the original object and the alias share the same mapping, properties and attributes (attributes can only be set on the original object), but they can be put on different places in the template (interface, container tabs etc.).
E.g. A fader that controls the volume of a midi device via CC 7 should be accesible on all of the three interfaces of a template. The "original" fader is defined in interface one. In all the other interfaces, aliases of the original fader objects are used to control the volume.
Saves time in changing the settings of objects that share the same functionality and saves some bytes in the template definition.

Not sure if I made myself clear about this topic. Hope that helps.
B.

[felusch]

OK got it...so an alias won´t work

I need to have it with different note on´s

here is my problemchild:
http://felusch.com/lemur/Bodo_Felusch_- ... -05-01.zip

the radio function of the interfaces labeled "4 Loops (1-8), ...(9-16),...(17-24) should be "linked" to have radio bahavior from 1-24 in each column.
-> any other idea for a workaround is welcome

thanks

[mat]

Hey,
haha...I am not sure if aliases now work proper, there was a problem in the beginning with it (although it is a nice idea!)
But you can also use a little script. It doesn´t matter if they are on different interfaces, interfaces are not part of the pathway on Lemur (but Containernames are!)
- create a script "inside" the Switch
- make execute on x
- fill in "Container2.Switch2.x=x" the remote the 2nd switch
- make the reverse way for remoting 1st switch... script inside 2nd switch, "Conainer.Switch.x=x"
If you do not make the script "inside" the Switches, you have to fill in the whole path for both sides...but it will work too.

Hope that helps
mat

[bxsj]

I've have used aliases successfully for what I've described above. And I've seen aliases being used in a lot of templates around here. But it's not mentioned in the manual. Is this another undocumented feature that will be abandoned in the future (like the gesture object)?
B.

[mat]

Sorry about aliases. I remember some bugs with that in the beginning, but I am sure they fixed that meanwhile.
It was just me, not trying to work with that after first experience - haven´t tried for years... (should do so before posting )
Thanks for putting that right and yes, aliases are a great thing!

However - if felusch wants to send the different messages with the linked buttons, I think he will need scripts anyway. Just wanted to point out that the interface name is not part of the pathway (a bit unusual, isn´t it?), while containers are (which is a good reason to put all controlls on an interface within a container, even if it fills the whole screen).....ah, ok, going offtopic - happy scripting all

cheers*mat

[bxsj]

Code: Select all

Just wanted to point out that the interface name is not part of the pathway (a bit unusual, isn´t it?), while containers are (which is a good reason to put all controlls on an interface within a container, even if it fills the whole screen).....ah, ok, going offtopic

Hmm, neither is a tab in a container part of the pathway as I recently learned ... </stop offtopic>
B.