Specifies generic undo/redo functionality at design time.
Assembly: System.Design (in System.Design.dll)
Adds an UndoEngine.UndoUnit to the undo stack.
Creates a new UndoEngine.UndoUnit.
Discards an UndoEngine.UndoUnit.
Releases all resources used by the.
Releases the unmanaged resources used by theand optionally releases the managed resources.
Determines whether the specified object is equal to the current object.(Inherited from Object.)
Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection.(Inherited from Object.)
Serves as the default hash function. (Inherited from Object.)
Gets the requested service.
Gets the requested service.
Raises the Undoing event.
Raises the Undone event.
Returns a string that represents the current object.(Inherited from Object.)
Theabstract class provides a default implementation of undo functionality at design time. An undo unit represents a single unit of undoable work. This unit is added to a stack and the user can then walk the stack to undo each action. Undo units typically are designed to toggle, which means that calling undo twice returns the application to its starting state.
Theclass takes advantage of the following characteristics of objects running within the designer:
All interesting objects can be persisted to some format by the designer loader.
All objects raise property-change notifications when a property is changed.
IDesignerHost offers the idea of transactions, which can be used to fabricate an undo action that spans multiple smaller actions.
With these features,can fabricate any undo units it needs automatically.
Do not change property values directly. The TypeDescriptor to change property values.class requires you to use the appropriate
monitors for change notifications to create undo units, and the units themselves consist of serialized object states. The following table shows the services that must be available when is created.
Saves property and object values for a component before and after a change is made.
Notifies the undo engine of changes made to components.
Used to track transactions.
The undo engine tracks transactions and creates a single undo unit that encompasses a transaction. As a result, the undo engine has control over the duration of an undoable action. Also, because transactions can be named, undoable actions inherit their names from the current transaction. If no transaction is available and a change is reported, the undo engine creates an undo name based on the type of change (for example, "Change property 'Text'").
Available since 2.0
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.