The parent should check how many children there are and lay them out. Then you avoid all that.

no

After the parent knows how many children there are, it can also know where to place itself so it is centered above the children.

you dont

as there can be several parents at the same level

@User uploaded a file:

But not when you start at the root. The point is that a parent with multiple parents at the same level is infact a child 🙂

this looks ok

So "inside dag" would place "kid 1" and "kid 2".

Somehow 🙂 hehe

well it looks way better then the previous one

listen I start at the root. it lays out kid1 and kid2, but as the root does not know how many kids (and the sizes) kid1 and kid2 have, it cannot determine where to place them so the grandkids have enough space

That's the whole point of computePrefWidth and friends.

so you would have the kids in a region and move the region?

Unless that doesn't make any sense?

If not, I guess all the Vertex instances must be children of the DagLayout and just maintain another property that points to it's parent (or parents)

they all are in the same group

let me try something then I will share the daglayout with you

OK

(and yes you may cry when you see it)

@User uploaded a file:

it leans to the left

now it leans to the right 🙂

@User uploaded a file:

Maybe the implementation of TreeView and TreeItem/TreeCell would be a good place for inspiration.

I gotta run, back later.

@edvin success

@User uploaded a file:

Very nice, @ron !!

And you can still move each Vertex individually, right?