Esther Trilsch

Another way to learn how the autorig components work is to click on the edit icon on the autorig component SOP. Its right next to the drop down for the components. This will expose the full apex script snippet for the component. Most of our pre shipped components have now been created with apex script. The button click will expose the code and you can then carefully study it or use it as a starting point for your own component

We also have it on our todo list to add mor code comments to existing components exactly for that purpose

graph::AddSubnet automatically returns the NodeId so you dont need graph::FindNode anymore to find the new node. you would still want to automate the name creation for the graph::AddSubnet though, very likely with something in the realm of the string::Format callbacks to procedurally change the name. One way or anothery you simply dont get around the fact that you need to give your new node a good name. it very much depends on your preference and your current implementation though what you use to create that name.

if you have multiple nodes matching the same name you would have issues in any case. Because it is then not clear anymore which node you want to find with the given path. And you ipso facto killed your humanly readable unique identifier. This is why the graph also tries to enforce unique patha. I can only recommend adding tags instead, and filtering by them.

If you already use a graph template and you just add a subnet why not use graph::AddSubnet and add the given graph template directly to a subnet? You dont need to stuff the content of your graph template then anymore in a subnet but you can work on the unpacked graph instead. And now that you are adding it as a subnet you can also give it a proper name and maybe even nice tags after you created it. Because you have now direct access to its nodeid. This should be a lot easier to manager.