Yea I tried that ... still same problem.

As to 'display form', that just means that (1) is done in the windows form load, and (2) means the form is now shown to the user, and everything after that is responding to events in the form controls...

A number of things:

1.  I have created a composite command with a specific custom title to programatically delete a box which is the main object in a group.  If I then do an Undo and check all the titles in the ActionUndone event, the specific custom title for the composite command I used to delete is never encountered in the ActionUndone event handler ... ???

2.  I have created a flowchart with 5 boxes, and created 4 arrows connecting the boxes, yet when I look at the flowchart.arrows collection, there are 10 arrows in the collection, with arrows having duplicate origin and destination nodes ... ???  ... does an arrow get created somehow for all the subordinate boxes too?

3.  I have created a small test app to attempt to demonstrate the issue I am still having with Undo/Redo, but my cut down version does not display the same symptoms.  Is there any other advice you can suggest to try and track down this problem?

I must admit that if I hadn't already spent as much time as I have in implementing your control, I would now be at the point where I would be looking at other products, as this feels like beating my head against a wall - at some point I am going to relaise that it hurts and stop!  You have been very helpful but my problem persists.

Then 2 could happen too after undo/redo if some command is not added to the undo history, but other commands rely on its result. I don't know how exactly that could happen. What we can do is send you a debug build of the dll, you rebuild your application with that dll and send us the .exe file so the developers trace through the flowchart's undo/redo code.

Or if you send us your project source I will get a developer here look through the code for what might go wrong. We can sign an NDA if needed.

Your UndoManager is also not recording and re-applying the visibility of the subordinate boxes attached to the group.  Based on some user configurable options, certain of the subordinate boxes are either visible or not.  If I delete a box which has some of the subordinate boxes Visible = False, when I undo the delete, they re-appear with Visible = True.

yes, it seems the groups Visible property somehow overrides the attached items' Visible when undoing/redoing.

I will have to check that with the developers tomorrow, it's a bit strange. There seem to be two Execute methods in CompositeCmd:

public void Execute();

and

public override void Execute(bool undoEnabled);

The first one should be called to close the current composite command and add it to the history queue. The second one is is used internally by the UndoManager and probably should not be called from outside. It seems that is implementation of the base Command class Execute(bool) method, which all commands should implement. I don't know why it's public though, it probably could be 'protected'.