- This topic has 13 replies, 2 voices, and was last updated 10 years, 9 months ago by
.
-
Posts
-
In the panel i am working on i get errors with setValue() in build 1500, in 1449 i have no problems & all works as it should.
Error i get is
lua runtime error At line[-1]:[C] What:C Namewhat: method Name: setValue Error message: No matching overload found, candidates: void setValue(CtrlrModulator&,int,bool,bool)setValue takes 2 boolean values, i’m sure you used to have 3, this all changed but your old setModulatorValue() calls should be fine, only the setValue() calls are different.
The two boolean values are
1. force – to force a change trigger even if the previous value was the same
2. mute – controls MIDI outputWhen in doubt always have a look at:
https://sourceforge.net/p/ctrlrv4/code/1503/tree/nightly/Source/Lua/CtrlrLuaModulator.cppand the magic what() method in the console
Thanks Atom, i found the offending scripts & modifying them now 🙂
Could it be that a few revs ago setValue only took one bool? I had them setup that way in the scripts that produced this error and they worked until now.
Cheerz,
HecWell it did take one but a long time ago, it’s possible. I saw people using setModulatorValue() so i left that unchanged, i think i’ll bring back setValue() with one bool so that no more errors pop up.
Mmmh, changing all to setValue(somevar,bool,bool) still gives the same error. I then changed them to the “old” way, setModulatorValur(x, bool,bool,bool) and this works again.
Moral of the story – imme stick to the old way for now 🙂
Please show me the exact code, it might be a type mismatch between int/bool.
Simultane posting – always good for a laugh!
Yeah, if it does not break anything please do, less typing 🙂
First fetch some midi data and trigger other functions when needed:
midiReceived = function(midi)
ID = midi:getLuaData():getByte(7)
LS = midi:getLuaData():getByte(9)
MS = midi:getLuaData():getByte(10)
......
....
...
if ID == 44 then setSamplezoneRoot(LS,MS) end....
end
And then the “helper” function, this produces the errors:
function setSamplezoneRoot(x,y)local rootnote = panel:getModulatorByName("sampleZoneRootNote")
rootnote:setValue(LS,false,true)end
Ok i don’t know if i get it, you define LS in one method, and pass it to setSamplezoneRoot() as parameters named x and y but you never use that you use LS in that method, this will work almost always but the ALMOST is a big problem. The LS variable might be used uninitialized and passed in as “nil” and this will cause problems, it has to be int (nil is a special type)
Lol i did not even spot this one!
I think i wrote this one in a sleepy moment, the other (similar) functions i wrote use the correct variables.Thanks Atom!
Yah, nil values have had me doing some funny stuff along the way. If it’s supposed to be an int value i force it to be 0 in the script that needs the value and then Lua is happy again – and me too 🙂
Well like i said you got lucky here, because ALL variables in Lua are global by default (unless declared local). But you should pay attention to the scope of your variables.
Also i recommend picking a naming scheme for your variables. If you keep them all caps it suggests constants for other developers, i try to sitck to lowercase notation, it’s an abbrevation of the hungarian notation: http://en.wikipedia.org/wiki/Hungarian_notation
i leave the type part, lua has no types. What i’m saying is, pick a method and stick to it.I just name the globals in caps to keep track of them 🙂
Thanks for the link, will keep it in mind for the future.
- The forum ‘Programming’ is closed to new topics and replies.