Right, above are the two custom nodes, you wont have the Link, FlowBlock, Node types and I cannot give them to you, you will have to strip these out of the objects.

Essentially I was using these custom nodes to encapsulate and associate our types with your diagram types.

eg.
a FlowBlock is contained and represented by a ContainerNode

a Node is contained and represented by a ShapeNode

a Link is contained and represented by a DiagramLink

Well, the control knows even less about what your diagrams show 8) FlowLayout is supposed to be used with something like sequence diagrams, and expects much guidance about what the nodes are used for. E.g. if the diagram shows some business process, with sequences of action nodes that describe some sub-processes displayed in different lanes, FlowLayout would expect you to specify the start and end nodes of the sub-processes, the index of the lane they should appear in, and the links in the sequence should be set as control-flow links. Some helper nodes that show associated data for the sub-process but are not part of the sequence could be displayed either above or below the control-flow line, as set through the sub-level positive/negative IDs.

We've also tried to adapt this class for arranging general flowcharts as in the Flow layout example, but that does not work that well. Now our developers are working on a new "FlowchartLayout" class that does some recursive decomposition of the graph and can recognize and arrange structures such as decisions and loops in program code. If your diagrams show something like flowcharts, we could send you a preview version of this layout if you wish to try it.

Stoyan

Here's a preview version:
https://mindfusion.eu/_beta/flowchartlt_preview.zip

The new class is called MindFusion.Diagramming.Layout.FlowchartLayout. It does not have any properties yet, so you can't customize node and layer distances, anchor points, etc. Also it is very strict on what kind of graphs it can arrange. E.g. it expects the flowchart to have only one start node (a vertex of zero in-degree), though if you have more than one, you can add a temporary start node that links them and the algorithm will find and use it as a decision node. The graphs should be susceptible to recursive decomposition, and links that lead to ambiguity would break the algorithm (such as a link that corresponds to a GOTO statement and jumps from one branch to another - the recursive function would not know whether it should follow that link or the normal control-flow sequence of the flowchart). Anyway we'll try to make it more forgiving for the official release, and add some keys that you could assign to LayoutTratis as hints for what to do in ambiguous situations. If the algorithm recognizes the graphs successfully as a flowchart, it will arrange it like this:



Stoyan

Seems the problem is caused by several double and triple links in your graph. Once we remove the duplicates, it runs much better. It's not perfect yet, but hopefully the released version will be

Stoyan

The latest version of FlowchartLayout arranges the graph as shown below, when the duplicated links are removed:
https://mindfusion.eu/_beta/fcnet_flowchartlt2.zip


If that looks close to what you need, we could ignore the duplicated links when analyzing the graph, and draw them at the same positions, but with a few pixels offset from each other when arranging.

Stoyan