Ok ... in testing to see which layout class caused this, I hit another exception.  I started with the Tree class.  I tried layout with rounded arrows and straight arrows, with centered, cascading and radial TreeLayoutTypes, and with various Directions.  All worked OK.  Then I did a number of UNDO operations until the end of the UNDO history.  Again all worked OK.  Then I tried a REDO, and immediately the following exception was thrown (just how stable IS this code???):

Message: Specified argument was out of the range of valid values.
Parameter name: Index was out of range.  Must be non-negative and less than the size of the collection.
Type: ArgumentOutOfRangeException
Source: mscorlib

Stack:    at System.Collections.CollectionBase.System.Collections.IList.get_Item(Int32 index)
   at MindFusion.FlowChartX.PointCollection.get_Item(Int32 index)
   at MindFusion.FlowChartX.Arrow.x3ebbf318c184de3b()
   at MindFusion.FlowChartX.Arrow.x06e06df617d17cf1(Graphics x4b101060f4767186, Pen x9c79b5ad7b769b12, Brush xe7ebe10fa44d8d49, Pen xfe39089439ac4f68, Boolean x2f9dabff87b2168b, Boolean x86c500fe5a9b7707)
   at MindFusion.FlowChartX.Arrow.Draw(Graphics g, Boolean shadow)
   at MindFusion.FlowChartX.FlowChart.x15edd106dba2f3b0(Graphics x4b101060f4767186, RectangleF xa6236fc5cd405c4e, Boolean x979174172ae18db3)
   at MindFusion.FlowChartX.FlowChart.x525e7084c19f09ac(Bitmap xcb82cf45bd90fc15, Rectangle xd1cff1e8f8666dbe, Boolean x979174172ae18db3, Boolean x650cceda2a9df79e)
   at MindFusion.FlowChartX.FlowChart.x525e7084c19f09ac(Bitmap xcb82cf45bd90fc15, Rectangle xd1cff1e8f8666dbe, Boolean x979174172ae18db3)
   at MindFusion.FlowChartX.FlowChart.OnPaint(PaintEventArgs pe)
   at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs)
   at System.Windows.Forms.Control.WmPaint(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.ComponentManager.System.Windows.Forms.UnsafeNativeMethods+I
MsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(Form mainForm)

thank you,

this version will fix the last issues:

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

The developer says that change cannot be detected at this time and is not repainted automatically. The same will happen with all members of Pen , Brush and StringFormat classes. We'll check whether that can be fixed.

For now you can assign a new Pen instance to the arrow.HeadPen, instead of only changing the DashStyle. Or at the end, after all changes, call flwChart.Invalidate to explicitly repaint everything.

Stoyan

Hi,

Thank you, version 4 is still in beta testing, we'll probably release it in the next couple of days. If you need it sooner, you can buy the component here

https://usd.swreg.org/soft_shop/32209/shopscr8.shtml

and we will send you the retail version 4 builds. Then we will send upgrades to customers by the end of the week.

Stoyan

Is there any possibility of getting a version of the DLLs that does not put your "Flowchart.Net Demo Version" text all over the show.  My salesman needs to demo new functionality in our software which includes your control, and cannot because of this as I have not been able to purchase v4 yet.

Thanks.

I have applied these DLLs. 

Unfortunately there still appears to be an issue with the Undo and group ZOrder.  I started a thread in the Discussions forum regarding the ActionRecorded event, and that it isn't being raised every time - I need a consistent means of setting buttons to reflect the dirty state of the flowchart.

If I open an existing flowchart diagram, and select on of my groups (which contains a box as the main node, plus a table and a couple of other boxes as subordinates), and then press the delete key, the group gets deleted, but the ActionRecorded event is NOT raised.

If I then create a NEW group programatically using a CompositeCommand, an ActionRecorded event IS raised. 

If I then select another old group and press the delete key, this time the ActionRecorded event IS raised.   ???

If I now progrmatically call the flowchart's UndoManager.Undo method, the group is recreated and appears on the diagram, but the ZOrder is only correct when the group is selected.  When de-selected, the subordinate items appear below the main item, while they were created above the main item.

Group is created with AutoDeleteItems = True.

1) Start with an empty flowchart, then create group-1 programatically.

2) Display form

3) Select group-1 on flowchart and press Delete key

4) group-1 gets deleted, but ActionRecorded event is NOT raised

5) User then does a mouse down and drag to create a new group (group-2) - I catch the BoxCreating event and start a composite command, then in the BoxCreated event I create the group using the composite command started in the BoxCreating event

6) ActionRecorded event IS raised

7) Then do an Undo ... and this is where it gets interesting ... group-2 is removed (as you'd expect because you are undoing the new group creation) ... BUT .... group-1 re-appears along with a messed up ZOrder