Currently the Skeleton.subSkel-class-function requires for the name of a given sub skeleton, which has to be defined in a special subSkels-dictionary-property.
Why so complicated? It would be much simpler if SubSkel directly expected a list of bones, which would then generate the particular sub skeleton. This list (or a tuple, set, etc) could of course be defined anywhere in the code of the respective project.
This would also simplify current custom projects which implement the logic of dynamic skeletons in a different way.
phorward
commented
8 months ago
Currently the
Skeleton.subSkel-class-function requires for the name of a given sub skeleton, which has to be defined in a specialsubSkels-dictionary-property.Why so complicated? It would be much simpler if SubSkel directly expected a list of bones, which would then generate the particular sub skeleton. This list (or a tuple, set, etc) could of course be defined anywhere in the code of the respective project.
This would also simplify current custom projects which implement the logic of dynamic skeletons in a different way.