Open Drakae opened 3 days ago
Are you getting the following layout when you use ELKT?
I tried auto-translating the given JSON into ELKT, and that's what I got.
What's interesting to me is that the layout is different in many ways, not just in the one node-edge crossing. In fact, it's a different graph:
UCA4
is quite long in the ELKT version. This is one thing that could lead
to a different layout. (And a different layout could remove a node-edge crossing just by chance.)Also @Drakae , maybe consider putting the JSON into a <details>
section to make this page easier to read.
@skieffer The json above also uses ports but they have a smaller size per default. But apparently this is not the issue @Drakae is facing, so I asked her to create an issue.
Originally, I set the size of the ports to (5,5). However, when using Sprotty the size is not applied if it is not used for rendering the ports. That is why this resulted in size (0,0) in the provided JSON graph. Changing this to (1,1) solves the problem.
@Drakae do you think the bug is a result of the node flexibility option?
@Drakae do you think the bug is a result of the node flexibility option?
Could be, at least for the given diagram deleting the option solves the problem.
Describe the bug An edge is routed through a node leading to a node-edge overlap. This only happens in the JSON format and not with the ELKT format. Graph showing the problem is in the comments because it is too big for this issue and for a link to elklive.
Expected behavior No node-edge overlap.
Screenshots Edge overlaps with the node "SC1"
ELK Version JSON 0.9.3 ELKT 0.9.1