glad to be of help. We've all been through it trying to get our code to work.
Keep a collection of techniques you use to accomplish certain tasks and it'll make the next template quicker and easier to create.
findchild question
Re: findchild question
Yes, I always collect the procedures and try to make smaller and for a better performance.
BTW, it would be great to have a Log file or a monitor to watch what's happening at any moment...
BTW, it would be great to have a Log file or a monitor to watch what's happening at any moment...
Re: findchild question
Hi All
Aren't you overcomplicating things?
You have a multiple Pad object and you want it to set values of another Pad object? And you want them set the same? Standard dot notation should work...
From Pad in Container1 have a script (executing on x) - Container2.Seq.Load.x=x;
From the Lemur 5 thread
One can no longer use the dot notation indirectly, by placing a dot after a variable that was set to point to an object.
dot notation is still supported, the only case it is not supported is when the part AFTER the dot is a variable referring to an object. in that case you should use setexpression()
See Monitor object - handy for debugging various things . .
i.e. From top level a Monitor with value = C2.Seq.Load.x should show the x values
findchild() seems handy for traversing hierarchies in a more controlled fashion when needed, rather then only having find object....
MM
Aren't you overcomplicating things?
You have a multiple Pad object and you want it to set values of another Pad object? And you want them set the same? Standard dot notation should work...
From Pad in Container1 have a script (executing on x) - Container2.Seq.Load.x=x;
From the Lemur 5 thread
One can no longer use the dot notation indirectly, by placing a dot after a variable that was set to point to an object.
dot notation is still supported, the only case it is not supported is when the part AFTER the dot is a variable referring to an object. in that case you should use setexpression()
See Monitor object - handy for debugging various things . .
i.e. From top level a Monitor with value = C2.Seq.Load.x should show the x values
findchild() seems handy for traversing hierarchies in a more controlled fashion when needed, rather then only having find object....
MM
iMac 2.8G i7 12G 10.6.8/10.7.2, Legacy Dexter/Lemur, Liine Lemur/iPad2, KMI SoftStep, 12Step & QuNeo , B-Controls, Mackie C4 etc
MaxMSP, Live Suite, Native Instrument stuff, etc Modified Virtual Guitar System etc All Projects/Modules © CC-BY-NC-SA[*][/b]
MaxMSP, Live Suite, Native Instrument stuff, etc Modified Virtual Guitar System etc All Projects/Modules © CC-BY-NC-SA[*][/b]
Re: findchild question
I'll try it later...It's so easy that I didn't think about it...
Thanks Macciza!