is it important to use else if?

if (m_cc == 0) d.Bass__Volume.x = m_ccv;
if (m_cc == 1) d.Snare__Volume.x = m_ccv;
if (m_cc == 2) d.Clap__Volume.x = m_ccv;

and

if (m_cc == 0) d.Bass__Volume.x = m_ccv;
else if (m_cc == 1) d.Snare__Volume.x = m_ccv;
else if (m_cc == 2) d.Clap__Volume.x = m_ccv;


is mostly the same and both is ok to use but....
lets make it like this to better explain:

if (m_cc == 0) d.Bass__Volume.x = m_ccv;
else 'do something else 1'
if (m_cc == 1) d.Snare__Volume.x = m_ccv;
else 'do something else 2'
if (m_cc == 2) d.Clap__Volume.x = m_ccv;
else 'do something else 3'

lets say m_cc is 2

it does the first "if m_cc==0"
and its not so it does the else instead (do something 1)
now it tries "if m_cc==1"
and its still not so it does the else (do something 2)
..........
now it tries "if m_cc==2"
and bingo m_cc is 2
so "d.Clap__Volume.x = m_ccv;" is now triggered
but it won't do else (do something 3)

does that make sense to you ?

This makes 100% sense. Its actually how I'm scripting the rest of my device! i just missed that i could do that here! THANK YOU!

The main reason i had it this way is because i needed to insert some custom code at each point to convert x to the right value. I can make that array a little more dense...

but... there is no way to store and call a function ref is there?

decl list={{'d.Bass__Volume', data_func},{'d.Snare__Volume', data_func},{'d.Clap__Volume', data_func}

{{1,2},{3,4},{5,6}} in lemur will just end up as {1,2,3,4,5,6} so list inside a list cant be done.


+ the list in example with setexpression is only to tell findobejct() what object to target.
The list is static and contains no possibility to store anything outside the script
So wouldnt make sense to start mix things into that list
If u want to store/recall variables when triggering the setexpression, you should create an expression outside the script.
And run it with same index number as the other one.

But forget about trying to combine one object target with another and store it in a variable.
You can combine 2 text strings into one and use that in findobject to run setattribute, getattribute, setexpression, getexpression. Nothing more or less..

Well I don't know what your main goal of project is or how the rest of scripts are done.
Or how much experience you have with lemur so hard for me to tell where the different ppl are in terms of lemur experiance.
So I just start my suggestions like ppl only have limited knowledge(just based on how limited Support I hat access to myself, when I was the clueless one).
Then ppl can always tell me that "Hey I'm not that clueless" and me like "Ok I STFU" hehe :-)

So if you feel this is best way for you, then no problem doing like that. .

I will just remind you that as long this is done inside a script then arrays are thx God only limited to 256 items and not 256 bytes. So your method is fine to do, but I really don't recommend doing the same with external expressions since they limited to freaking bytes (why o why o why o why liine???)
I did some of my first more advanced scripts in lemur where I hat expressions like this, [0] the name of the item [1] midi Val, and it was cool until I started use all knobs n parameters I was like WTF why are only half the values being recalled...
and turned out before even half the parameters was stored it eaten up the whole expressions array because some names took more bytes than others.

That's the only reason I said that other thing.

In the end I just found it easier to have separate settings lists, that stores /recall With the same index vals as the name index.
I'll explain later below:

The funny experience for me was Lemur was my first programming lang to learn until then I was more a script kiddie type.
So for me my programming knowledge was only based on what lemur could do, picture how mind blowing it has been for me learning Python and I can fucking pack all settings name whatever under a single value and just call them with sub calls or make dynamic strings to call functions and save them as value and do that value with a .name whatever. Booooooooooooooooooooooom.......

Looking back at all this I can only say that maybe lemur do needs a bit of an upgrade in its scripting lang. Lmao.
But I still like the nature of lemur where half if it can be done by GUI and rest done by coding.
Vs almost full time coding.
+ when it comes to recalling and storing variables then it is possible with dynamic strings in complex ways like the other programmings langs, without 2000 if rules.