The fix will be available with version 4. With a purchase you get free upgrades for six months, so if you buy the current version, you will also get  version 4 when it's released.

Anyway, the Flowchart.NET evaluation dlls are not functionality or time -limited, so you can develop your application with them.

Stoyan

I can't give any advice whether to purchase or when to purchase Version 4 will be out in a couple of weeks if there aren't any hard to fix bugs reported by testers.

Regarding layout, by default the layout classes treat each item in a group as a distinct graph node. To fix that, set the IgnoreLayout property of the subordinated items to true, so the layouts won't change their position. Thus the subordinated items will just stay attached to their master nodes.

Another option is to enable the KeepGroupLayout property of layout classes before calling Arrange. That property is not documented, but it functions almost the same way as if all group subordinated items have IgnoreLayout = true.

The difference between the two methods is how the layout routines calculate the nodes size, the former method uses only the bounds of the master item, the latter uses the rectangle that bounds all items.

Stoyan

I have downloaded the latest beta from the link you provided.  I have set the IgnoreLayout property of the subordinate group items to True, which reems to have resolved the layout issue, BUT, the ZIndex problem is NOT fixed.

1)  I delete a group, do an Undo, and the small box (with image) has disappeared, and the table (used for caption) is only visible when the group is selected ... when the selection is elsewhere, the table disappears!!!

2)  There is also a bug in the layout managers.  I have created nodes with very specific anchor points around the edges, and set the flowchart SnapToAnchor property to OnCreateOrModify, yet when I perform a layout using the layoutmanager, some of the arrow connections are made to the centre of the nodes (which do not have an anchor).
I also got an exception thrown when doing an UNDO of a layoutmanager action.

Though as we tested this further it seems redoing the composite breaks the Z order too, so we'll have to save the Z order array in the 'before' and 'after' states and restore in also when redoing.

Set the Anchoring property of layout classes to Reassign and the arrows won't connect to the box or side centers but to some anchor point. Regarding undo of layout actions, that's automatically recorded in its own composite command, you don't have to create one. We can't see any problems when undoing or redoing the layout.

Yes, that null terminator is appended unduly to the StringBuilder and turns up in the string. For now you can use String.TrimEnd to remove the null.

The developer has already removed the Append(null) call anyway; these dlls are freshly built:

https://mindfusion.org/_temp/FlowChart.NET.zip