Link not following the shortest path


I have a pretty complex diagram as shown in the image below.
Each node has multiple links coming in and out of them.
The image
just shows a part of the entire diagram.
I have used
LayeredDigraphLayout(Direction=“90” SetsPortSpots=“False”

ColumnSpacing=“15” LayerSpacing=“10” LayeringOption=“OptimalLinkLength”

Also in my route definition - <goxam:Route
Routing=“AvoidsNodes” Curve=“JumpOver” FromSpot=“AllSides”

ToSpot=“AllSides” />

This seems to layout the diagram in the
best possible way amongst the various options I have tried.
thing that seems to go wrong is, if you see the links between the nodes -
“HasSource” and “HasSetPoint” - this seems to take a longer path. The
links should have been drawn as straight lines, instead if going right
then left in a loop and then getting connected to the node.

can I avoid this? Also if you have any suggestion on how to layout the
diagram better, please let me know.

Which platform/version are you using?

I know we had improved some of that routing behavior a while ago, but I’d have to look up exactly when and for what cases.

I am using assembly version (of Northwoods.GoWPF.dll) in VS 2008.

I’m investigating this. I haven’t been able to reproduce this exact problem, but I was able to reproduce some routing that could be better.

I checked the source revision history but couldn’t find the changes we made that I remember addressed this kind of problem. Maybe I need to search again.

Part of the problem is due to there not being enough room between the layers for the links.

If you increase the LayerSpacing value slightly, does it help? Try 20 or maybe a bit more.

I tried increasing the layer spacing to upto 25 and even tried increasing the column spacing, but it did not seem to work.

What i don’t understand is, the links could have been placed as straight lines between the nodes, but it seems to be going in a loop ( which is unnecessary) and then joining with the node.
Also in spite of mentioning “AvoidNodes” some links cut across the nodes, as you can see in the image I had attached earlier.