-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Layout option to force global container: root
coordinates for all children and edges
#1012
Comments
Hi snemsi, |
Sorry, I don't follow you. Is there a way to force all childrens/edges to use global root coordinates? |
No, not that I know of. |
Hi @snelsi, as I understand it, you want to be able to configure whether to use absolute or relative coordinates. This is currently not possible and also probably out of the scope of ELK. Is there any obstacle to simply computing the absolute coordinates from the layout results produced by ELK? |
This should be addressed when fixing #901 |
I'm currently using elkjs along with xyflow/react and integrating my custom edge renderer.
This means I have to calculate and convert all edges to absolute coordinates, which is a bit inconvenient and increases the chance of mistakes. I had hoped that elk would provide an option to use flat children/edges output with absolute coordinates. |
I see, I previously misunderstood the problem. |
New to Elk , I will be glad for any help.
I have a nested layout with cross-parent edges.
After enabling
"hierarchyHandling": "INCLUDE_CHILDREN"
layout option, I noticed that some of the edges are usingstartPoint
/endPoint
sections relative to thecontainer
coordinates they are located.Is there a layout option I can enable to force all children and edges to use global
container: root
coordinates instead?The text was updated successfully, but these errors were encountered: