incorporating another delimiter to the data string to locate each record would work for undetermined record sizes
something like record = “copy0(0,0,0)copy1(2.5,53.369,90)copy2(15,-56.222,0.5)” which can be built using the set method upon an action
first find the string “copy” & copy, then use that position plus 1, to find pos1 “(” then from there the position of “(” plus one can find pos2 “)”
then this_record =mid(record,pos1+1,pos2-pos1-1)
then you use the comma delimiter to separate the data to the required field
in regards the position change, you could use polar coordinates, a set distance (option to change) * cos or sin of angle (option to change)
ie for stepping distance of dist=10, and a angle of Z_rotation
x = distcos(RotZ)
y=distsin(RotZ)
as per your calculations
its recommended that the DC axis is center to the bar object, so acts as a point, without the worry of the bar size (which can be another option to change)
the animation of RotZ would be determined by the directions adding, taking or none of angle change nominated.
attached example requires more work, the information is not transferred directly to the copy bar, can’t pass the data without a redraw. click on the first bar triggers redraw. However serves as an example to how the data string is created and used.
direction copy3.skp (48.7 KB)
Will return to the first model where the trigger and copy are one same level and update immediately. The negitive movement is incorrect, so needs work as well.