I hate when these scripts get red. I guess that in this case, the idea would be to create an array of object names or just store the getobject value in an array, then access these object indirectly to avoid scipting errors.Softcore wrote: Once FaderX was destroyed, the script that was set to destroy it became red because there was no FaderX anymore to destroy lol!
Not sure I get this right, but of course you would have to create the mapping yourself in a user function likeBTW, we are not able to set any midi-OSC mappings via scripting so we are limited to scripted outputs for the created object I guess.
midibyte = scale(x, imin,imax, omin,omax)
For simple things I find it better to use the settings directly on the object in the editor, but for more complex coding I found it way easier to deal with that stuff myself. I use to set all my settings in some global init function where I could write some info, which is much easier than having to go thru a bunch of objects to see what's going on.