public abstract class Operation : System.IDisposable
Public MustInherit Class Operation Implements System.IDisposable
public abstract class Operation : System.IDisposable
Public MustInherit Class Operation Implements System.IDisposable
To participate in the undo/redo framework, an Operation must be created and added to the appropriate ArcGIS.Desktop.Framework.OperationManager. There isn't one operation stack for the application, each Pane and DockPane decides how its operations are managed. For example, different maps have their own operation stack; deleting a feature in one map will not be undoable if the focus switches to a different map. Although each Pane and DockPane are given the opportunity to provide their own OperationManager, they may elect to share the same one. For example, all map panes rely on an OperationManager managed by a Map object. This way, all the map panes for the same Map share the same OperationManager. In this case, deleting a feature will show up in the undo/redo stack for all map panes showing this Map.
Operations can also be categorized so that operations belonging only to a specific category can be undone. For example, ArcGIS Pro has editing and mapping operations; if these operations are intermixed, users can elect to just undo the editing operations and skip over the mapping operations. Categorized operations must be mutually exclusive.
System.Object
ArcGIS.Desktop.Framework.Contracts.Operation
ArcGIS.Desktop.Framework.Contracts.CompositeOperation
Target Platforms: Windows 10, Windows 8.1