File	Doc	Category	Size	Date	Package
UndoableEdit.java	API Doc	Java SE 5 API	4040	Fri Aug 26 14:58:22 BST 2005	javax.swing.undo

UndoableEdit

Fields Summary

Constructors Summary

Methods Summary
public boolean	addEdit(javax.swing.undo.UndoableEdit anEdit) This UndoableEdit should absorb anEdit if it can. Returns true if has been incorporated, false if it has not. Typically the receiver is already in the queue of a UndoManager (or other UndoableEditListener), and is being given a chance to incorporate anEdit rather than letting it be added to the queue in turn. If true is returned, from now on anEdit must return false from canUndo and canRedo, and must throw the appropriate exception on undo or redo. param anEdit the edit to be added
public boolean	canRedo() True if it is still possible to redo this operation.
public boolean	canUndo() True if it is still possible to undo this operation.
public void	die() May be sent to inform an edit that it should no longer be used. This is a useful hook for cleaning up state no longer needed once undoing or redoing is impossible--for example, deleting file resources used by objects that can no longer be undeleted. UndoManager calls this before it dequeues edits. Note that this is a one-way operation. There is no "un-die" method. see CompoundEdit#die
public java.lang.String	getPresentationName() Provides a localized, human readable description of this edit suitable for use in, say, a change log.
public java.lang.String	getRedoPresentationName() Provides a localized, human readable description of the redoable form of this edit, e.g. for use as a Redo menu item. Typically derived from getPresentationName.
public java.lang.String	getUndoPresentationName() Provides a localized, human readable description of the undoable form of this edit, e.g. for use as an Undo menu item. Typically derived from getDescription.
public boolean	isSignificant() Returns false if this edit is insignificant--for example one that maintains the user's selection, but does not change any model state. This status can be used by an UndoableEditListener (like UndoManager) when deciding which UndoableEdits to present to the user as Undo/Redo options, and which to perform as side effects of undoing or redoing other events.
public void	redo() Re-apply the edit, assuming that it has been undone.
public boolean	replaceEdit(javax.swing.undo.UndoableEdit anEdit) Returns true if this UndoableEdit should replace anEdit. The receiver should incorporate anEdit's state before returning true. This message is the opposite of addEdit--anEdit has typically already been queued in a UndoManager (or other UndoableEditListener), and the receiver is being given a chance to take its place. If true is returned, from now on anEdit must return false from canUndo() and canRedo(), and must throw the appropriate exception on undo() or redo().
public void	undo() Undo the edit that was made.