as the vertices contain the kids, the layout is done recursively

@User uploaded a file: Untitled

the screenshot is actually made by this method

doLayout gets started from the layoutChildren method

My idea in with the filtered list is to find out what is already there on the same Y coordinate

once I know where they are I can find out what distance to use

does that make sense?

I think you should use the already available methods to perform calculations on size, like

computePrefWidth

etc. They should check how many children they have, ask them how wide they want to be and add padding, then return that number. I haven't thought this completely through, so there may be issues. I'd like to help out with this, but I won't have time before next week :((

even if you use computePrefWidth you have to find all the vertices that are on the same level (layoutY level)

@ron Yes, but I think that the parent will ask it's children, not the other way around.

Again, haven't thought this through but that seems much more logical to me.

ah but the parent does not know if he is at the same level as another parent (one of its siblings)

But it's parent will know 🙂 hehe

I'm serious though 🙂

I am thinking

that way of going up and down the data.... does not sound like fun

You should only go down, 100% sure of it.

yes

I need to clean up that code and see what I actually need

instead of dumping everything on long lines

@ron What I sometimes do is take advantage of the Node.properties object or the Node.userData to associate things like level with the Node itself. For example, do n.getProperties().put(”level”) if you want to save off a level instead of going up and down a graph to re-familiarize your program with the model state. That’s different that what you’d do with a forms-based application which moves more to consolidating data like that, but I’ve found that a few well-placed properties make the whole program simpler when trying to make drawing decisions.

node.properties? @carlw I could kiss you!!!!!

that would actually work

and work quite well

See I learn something everyday in this channel

Hi, quick question! What if exception is thrown in runAsync block? Is it retrown so I would have to enclose it in try catch, or there is a better way to handle it?

yeah...i have a fair amount of "data" put in properties like this

i'm no djikstra, but i'm pretty sure the fastest tree walking algorithm is a O(1) lookup of a property

@ron I think we're going to see more of what you're doing as the graphics of FX becomes a real selling proposition for business applications.

@jakub.dyszkiewicz Does this work for you?