Open zozorg opened 7 years ago
Just create a skeleton with 3 bones, duplicate it, and move the bones around.
Yes, I see what you mean. When I duplicate skeleton layer (within the same document) it creates copy of each bone. But those copies still reference parents from old skeleton.
In general any copy operations related with bones are dangerous at the moment. For example this one - #455.
Posted a $50 bounty
+$10 bounty, total $60
I'm taking a look at this issue now.
Update 2020/1/13 I think I figured out what the issue might be. I'll be trying something.
I've been looking through the source. I think part of the problem is that the design of the bone/skeleton relationship is not very structured. Bones are just there: they don't belong to anything. Is this by intention?
I did a little sleuthing with Python to investigate how bones & skeletons are structured. I'm very visual so I wanted to see how they were networked and I attached my findings below.
Taking a cue from Blender, I propose skeletons take on a more active role, so that a user can select a skeleton, double click, and enter the skeleton group to modify the bones.
Does this work for the design?
@src-r-r The possible cause of this problem is a wrong duplication of the ValueNode that build the relationships among bones themselves. Maybe LayerSkeleton should override Layer::clone() method to fix the bones' parenting after duplication.
Synfig version & platform: linux 1.3.4
Issue description: When copying a skeleton and its linked splines, by copy/pasting or embedding an imported canvas, the resulting skeleton isn't linked to the splines.