I think the loop is happening internally as I have only mapped midi to one of the Ring Area objects. The if statement has fixed the problem. ThanksSoftcore wrote:Also, as mentioned earlier, by linking the two objects you dont have to midi map both of them - only the one, perhaps thats why they are being "locked" for you?
More options for Alias controls
Last edited by acidan on 15 Apr 2013 16:29, edited 1 time in total.
Re: More options for Alias controls
I am trying to target switch 1 of a Switches object (an 8 switch array set to radio mode) from a Pad object on another page (just 1 pad).
the script I have used is: Switches.x=1;
all of the switches are pressed so I know that I am targeting the right object. I'm just struggling with the array part.
Any help would be great.
Cheers
the script I have used is: Switches.x=1;
all of the switches are pressed so I know that I am targeting the right object. I'm just struggling with the array part.
Any help would be great.
Cheers
Re: More options for Alias controls
Objects' arrays (vectors in Lemur) are simply accesed by referencing their "index" number in []
The first switch of an 8 switches-object for example would be
Switch.x[0]
So you need
These things are all covered in the manual though - it would be best if you just gave it a read!
The first switch of an 8 switches-object for example would be
Switch.x[0]
So you need
Code: Select all
Switches.x[0]=1;
Re: More options for Alias controls
Really appreciate your help Softcore, I tried many combinations like this but had the [0] in the wrong place!
I do have the manual and I am slowly starting to understand some basic functions. Ive not had any previous programming experience at all so sorry for asking silly questions.
Switches.x[0]=1; worked a treat! but has given me another problem!
when switching the target radio Switches, the previously selected Switch remains the same colour as if its still selected, as well as the current selected switch
Do I need another script to fix this?
Thanks
I do have the manual and I am slowly starting to understand some basic functions. Ive not had any previous programming experience at all so sorry for asking silly questions.
Switches.x[0]=1; worked a treat! but has given me another problem!
when switching the target radio Switches, the previously selected Switch remains the same colour as if its still selected, as well as the current selected switch
Do I need another script to fix this?
Thanks
Re: More options for Alias controls
No such thing as a silly question!
I see what you mean - not "selected" but "on"...it stays "on"...this is because the "radio" functionality only works when you "touch" the object....
So in essense, what you want is as soon as you tap on that other pad, the first switch is activated (on) and any other switch that was previously on should go "off" (like it would if you use it in "radio" mode)....
So.....
you need this script in your Pad
What this does essentially is giving the "i" variable values from 1 to 7 and then applies the script in the { } ....
So its a "fast way" of saying:
Switches.x[1]=0;
Switches.x[2]=0;
.....
Switches.x[7]=0;
I see what you mean - not "selected" but "on"...it stays "on"...this is because the "radio" functionality only works when you "touch" the object....
So in essense, what you want is as soon as you tap on that other pad, the first switch is activated (on) and any other switch that was previously on should go "off" (like it would if you use it in "radio" mode)....
So.....
you need this script in your Pad
Code: Select all
decl i;
for (i=1; i<8; i++)
{
Switches.x[i]=0;
}
Switches.x[0]=1;
So its a "fast way" of saying:
Switches.x[1]=0;
Switches.x[2]=0;
.....
Switches.x[7]=0;
Re: More options for Alias controls
I ended up using the latter script u suggested (and obvious now its in front of me!) It works and is easy for me to apply to other objects in my template. I need to read a bit more to understand whats actually happening in the first script.
thanks again
thanks again