Objective-C Code

 
-(void)undo:(id)sender; 
-(void)redo:(id)sender; 
-(void)revert; 

Objective-C Code

 
-(void) revert:(id) sender; // as a target action  method for Interface Builder

Java Code

 
public native void undo (); 
public native void redo (); 
public native void revert ();

When you send the undo or redo messages to an editing context, they are forwarded to its undo manager. The undo method closes the last open undo group and then applies all of the undo operations in that group (recording any undo operations as redo operations instead). The redo method likewise applies all of the redo operations on the top redo group.

Note that undo is intended for undoing top-level groups, and should not be used for nested undo groups. If any unclosed nested undo groups are on the stack when undo is invoked, an exception will be raised. To undo nested groups, you must explicitly close the group with an endUndoGrouping message to the undo manager, then use undoNestedGroup to undo it.

While undo only performs undoing of top-level groups, revert is a more extensive undo . The revert method removes everything from the undo stack. It throws out all insertions and deletions and restores the updated objects to their last committed values.

Note that revert does not cause a refetch from the database. It also does not replay the entire undo stack. If you add your own operations to the undo stack, they may not be properly reverted. The revert method also does not undo changes in display groups. Display groups that allow insertion and deletion of objects must be refetched whenever their editing context is reverted so that the user-interface display can be properly synchronized.

Usually, you do not need to write any code, and can simply connect your user-interface widgets to the appropriate undo, redo, or revert operations using Interface Builder.

Note The EOJavaClient framework released in EOF 3.0 does not support undo.

Caveats

NSUndoManager does not retain the targets of undo operations. However, it does contain references to the targets of the undo operations since it needs them to send undo messages when undo is performed.

Therefore, to avoid objects being leaked as your application runs, you should remember to clean the undo stack periodically.

For example, you could clean the stack after a save operation with the following message, or wherever it is appropriate depending on your undo policy. Note that, from a database access perspective, it is not recommended to allow an undo past a prior save point.

 
[[editingContext undoManager] forgetAllObjectsWithTarget: editingContext];