Quote:


See attached layout screenshot for your last file with additional OrthogonalRouter.Arrange call. It does not contain "end-if" nodes where branches of previous "if" nodes merge, as FlowchartLayout expects, and so it cannot determine any nesting for the decision branches. Your links look more like goto-statements, and we don't have support for such in FlowchartLayout yet. If you prefer FlowchartLayout anyway, you will have to re-route such unsupported links in an extra step, e.g. the attached layout image also has OrthogonalRouter applied:

FlowchartLayout layout = new FlowchartLayout();
layout.IgnoreRepeatingLinks = true;
layout.Arrange(diagram);

OrthogonalRouter router = new OrthogonalRouter();
router.Arrange(diagram); 

DecisionLayout seems to create better results with your graphs as in second image. The kind of long U-bends as in "Yes: next iteration" link near the top will be fixed for the official release in a few days.

Stoyo wrote on Jun 10^th, 2014 at 7:57am:



As per above comment we will try to do changes if possible, Can u send me xml which explains merging of IF at End-IF so that i can try.

Please point out what's wrong with my XML because I am not getting closing node and opening node.

Simply i m giving origin ID and destination ID to draw links.

Its not possible to add END-IF for each IF, Is there any solution on this .

I am providing origin ID and destination ID for each node then why its intersecting Its very simple why did you requires these all stuff, I am not getting.

The pairing is also needed for loop / end-loop nodes. The "next iteration" link returns back in the flowchart, so it's origin is an end-loop condition, and you must add a corresponding start-loop instead an end-if for it, enclosing the decision section from CA-VIDEO-NUMBER. I have just moved the link VID-SUB -> CA-VIDEO-NUMBER to your helper node instead to use as loop start, you can find the file and layout image attached.

The remaining decision branches from VALID-DATA and CA-VIDEO-NUMBER already merge into common end nodes (VID-SUB =... and End Of...) so you don't need additional end-nodes for them.

If you will be generating nodes in this format, also remove any OrthogonalRouter calls after FlowchartLayout; FlowchartLayout will set better link paths as in attached image.

If you are generating these flowcharts from source code parser, you should really check the JavaScript sample project, it shows how to handle if statements, switches and loops.

I hope that helps,
Stoyan

No, that's not the same. If you know a bit of graph theory, what this algorithm does is to look for distinct cut pairs in the graph. The subgraph between each cut pair is drawn either as an if, switch or loop depending on the number of links starting from them and the links' direction. So you must create pairs of nodes in the graph that define start and end of conditions and loops, and you cannot use same node in different pairs. In your XML you were trying to use a node as both a start of condition block and as the end of a loop, which prevents us from finding distinct cut pairs. Moving the link fixed that, now you can see the distinct cut pairs are endif + not(vid) and CA-VIDEO + VID-SUB.

Creating such paired nodes is easy if you are building flowchart from source code, but relying on them prevents FlowchartLayout from working well with any arbitrary graph. So if you cannot create your graphs in that format, better use the new DecisionLayout. For a future release we'll try to provide a different way for defining node functions such as if/switch/loop instead of relying on the graph structure.

The files we have from you all look pretty good when arranged with DecisionLayout, if you have examples that don't work well please send as many as you can to support@mindfusion.eu and we'll try to improve. You can find latest build here, it now also creates shorter U-bends as in attached image:
https://mindfusion.eu/_beta/netdiag511.zip

Longer U-bends issue is still not resolved in your latest version.