Unexpected connections in the diagram

[tk0miya]

Hi,

I am on blockdiag 1.5.3 and I don't quite fully understand why in the output diagram there are connections from:

• collect.user.data -> accept.redirect
• accept.cookie -> accept.redirect

They really should not be there - I don't understand why they are added?

I'm using a diagram definition as below and the diagram is attached.

blockdiag {
   orientation = portrait;
   default_shape = box;
   node_width = 200;

group {
  orientation = portrait;
  color = "#ccccdd";
}

   begin [shape = beginpoint];

   begin -> collect.user.data;

   collect.user.data -> accept.cookie;
   collect.user.data -> rejected;

   accept.cookie -> redirect.user;
   accept.cookie -> rejected;

   redirect.user -> accept.data;

   accept.data -> accept.redirect;
   accept.data -> rejected;
}

---

• Bitbucket: https://bitbucket.org/blockdiag/blockdiag/issue/70
• Originally reported by: Dariusz Suchojad
• Originally created at: 2015-11-17T17:17:46.185

[tk0miya]

From Takeshi KOMIYA on 2015-11-29 02:21:45+00:00

Sorry for inconvinience.
It is unexpected behavior. but it is hard to fix.
I will fix it in the future. Maybe, it will fixed at v2.0.

[jstallkamp]

Any chance for a fix for this one? It messes up one of my diagrams as well. The edge routing overlays different edges, leaving the impression of connections/edges that must not be there.

BTW, I just noticed that the layouting seems to work for vertically running edges. Only the horizontally running edges overlap.
You can see this, if you change the orientation to landscape in the example in the original post.