What is the best strategy / approach for balancing and aligning the contents of a node with the graph

[BCampbellDev]

Trying to create a link to the model errors so I am attaching the json.

scratch_548.json

So our goal is to center and balance the contents of the child nodes so that the edge leading to the hierarchy / wrapping node, would end at the center of the first child node.

The wrapping / parent nodes will not be shown to our users, so for our users, we want it to look like the edge leads to the first child node - same for the last child node and the edge leaving the wrapping / parent node.

Solutions we thought of:

• Adjust the padding of each wrapping / parent node so the contents are centered against the edge targeting the wrapping / parent node
  OR
• Use fixed positioning on the wrapping / parent node's in and out port to align them against the center of the first and last child nodes

Seems each approach has its own pros and cons. I've worked on the padding solution but run into some issues, so was hoping to get some feedback on what the best approach might be or alternative approaches.

Thanks in advance!

[soerendomroes]

Hi, have you tried using a port (that looks like a node) with a fixed position instead? Currently, top node of the inner graph does not seem to be connected to the outside. If this produces bends, I suggest to add straightness priority to the edges that require it.

Adjusting the padding has the problem that this would change the size of a node, hence you would need to post process the drawing and adjust all node positions.

[BCampbellDev]

@soerendomroes yes thats what im running into with the padding solution, finding i would need to run the layout when I make an adjustment.

I think what you are suggesting, and correct me if I am wrong, is the fixed positioned ports correct? So i would take the outer nodes in port, on the north side, and set its position fixed to where it would look centered against the first inner node?

[soerendomroes]

Yes, but it has a similar problem that you need to know where the center actually is before you know how big the node might be.
Currently, I do not see that it is possible without doing more than one layout to calculate the size and then set position/padding based on that first calculation.

[BCampbellDev]

agreed - thanks for your feedback - i will dive into the fixed positioned port solution :)

[BCampbellDev]

@soerendomroes i tried that port solution, starting running into issues due to needing fixed position and the layout algorithm. Solution ended up being a lot simpler. I configured the model to be setup for hierarchy in a better way, by setting the hierarchy handling to include children and setting merge hierarchy edges to false - then I was able to set the edges to connect directly to the first inner node. Problem solved! lol thanks for all your help.