MindFusion.Diagramming for .NET MAUI diagrams can be just a part of the data model of your application, which might already have undo/redo functions implemented for its native data. To integrate MindFusion.Diagramming for .NET MAUI undo functionality into the application's undo mechanism, use the ActionRecorded event. When the event is fired, add a corresponding wrapper-record to your application's history from the event handler. The wrapper could just call Undo and Redo methods of the UndoManager. In such situations make sure the MindFusion.Diagramming for .NET MAUI's history Capacity is at least as big as your application's.
Another possibility is to reuse MindFusion.Diagramming for .NET MAUI's undo functionality by subclassing Command and creating classes responsible for changes in your application's data. When a change occurs outside the diagram, it can still be recorded by calling the Diagram's ExecuteCommand method and integrated into MindFusion.Diagramming for .NET MAUI's command history.
A simpler scenario when you might have to subclass Command is using complex objects as tags or embedding controls in ControlNode instances. Actions that change these objects or controls cannot be detected and handled automatically by MindFusion.Diagramming for .NET MAUI. To integrate such an action into the diagram's undo history, you must create a Command instance that knows how to carry out, undo or redo the action.
Command subclasses must implement Execute, Undo and Redo methods. Actions represented by your subclass must be carried out by executing the ExecuteCommand method of Diagram. ExecuteCommand invokes Execute on the command passed as argument, which is then added to the history queue and whose Undo and Redo methods can be called multiple times later by the undo manager. Usually you can implement Redo as a call to Execute, but if the latter is time consuming, its result state can be saved in an instance member and restored by Redo.
Do not call the Undo and Redo methods of your class directly, just implement them and they will be invoked by UndoManager's Undo or Redo methods when necessary.
The example below shows a simple implementation of Command methods:
C# Copy Code |
---|
public class PersonTag |
Visual Basic Copy Code |
---|
Public Class PersonTag |