Better guess than any I had. No idea why just about any component number returns something, even a changing value.hayasidist wrote:I think it's an index to the settings for the separate x,y,z handles --synthsin75 wrote: ... I don't know what all the bezier "components" mean ...
a quick look at a file's internals for a 3d Bezier key (actually layer translation in this case) with a "loop" to the next:
{"im":9,"v1":-1.0,"v2":-1.0,
"b":[
{"ao":0.183271,"ai":-0.152106,"po":0.205828,"pi":0.15657},
{"ao":-0.099733,"ai":-0.035167,"po":0.287141,"pi":0.36332},
{"ao":0.000011,"ai":0.013836,"po":0.386905,"pi":0.315506}
],
"in":1,"h":0,"s":false,"t":0}
So a straight guess from me: component 0,1,2 => x,y,z; no idea what would happen if you tried to set / get one that was greater than the dimensionality of the item..
I did that for easy reference. The docs are listed in ID order, but mohoscripting.com isn't. I've already emailed Stan about maybe getting an ID column for Moho constants.((A complete aside: noted that you have the types / modes in a comment at the end; those are globals with, IIRC, a MOHO. prefix should you prefer to use the constant name rather than the value))
Yeah, I know I could use the names, but some of those "if" statements were long enough already.