From b28ad987327d89ec393168d68d044be0405081c3 Mon Sep 17 00:00:00 2001
From: "Frank Schoenheit [fs]" Changes to a document usually result in recording of information how to undo those changes, if desired. A so-called
- Undo action records the information how to undo a single change. Undo actions are maintained in a stack, so that
+ undo action records the information how to undo a single change. Undo actions are maintained in a stack, so that
the changes they represent can be undo in the reverse order they have originally been applied.Undo
Redo
@@ -52,15 +52,15 @@ interface XUndoManagerListener;
stack, so it is possible to re-apply the changes to the document.
For collecting multiple changes in a single Undo action, so-called Undo contexts are provided. When an Undo - context is entered, all subsequently added Undo actions are not pushed onto the Undo stack directly, but considered - a sub action of the Undo context. Once the Undo context is left, a single Undo action is pushed onto the Undo stack, +
For collecting multiple changes in a single undo action, so-called Undo contexts are provided. When an Undo
+ context is entered, all subsequently added Undo actions are not pushed onto the undo stack directly, but considered
+ a sub action of the Undo context. Once the Undo context is left, a single undo action is pushed onto the undo stack,
which comprises all those single Undo actions.
Undo contexts can be arbitrarily nested.
Hidden Undo actions are those which in no observable way contribute to the Undo stack. That is, - any method retrieving information about the stack will behave as if the Undo action does not exist. Nonetheless, +
Hidden Undo actions are those which in no observable way contribute to the undo stack. That is,
+ any method retrieving information about the stack will behave as if the undo action does not exist. Nonetheless,
calling
Hidden Undo actions can be created by calling
An Undo manager can be locked and unlocked, using the
A hidden Undo action does not, in any visible way, contribute to the Undo stack. This means +
A hidden undo action does not, in any visible way, contribute to the undo stack. This means that -
The redo stack is cleared when a new hidden Undo context is entered.
@throws ::com::sun::star::util::InvalidStateException - if the Undo stack is currently empty, in which case it is impossible to push a hidden Undo action onto + if the undo stack is currently empty, in which case it is impossible to push a hidden undo action onto it. @see emterUndoContext @@ -131,10 +131,10 @@ interface XUndoManager /** leaves the undo context previously opened viaIf no Undo action has been added since the context has been opened, the context is not only left,
- but silently removed, and does not contribute to the Undo stack at all. In this case, possible
- listeners will be notified via
If no undo action has been added since the context has been opened, the context is not only left,
+ but silently removed, and does not contribute to the undo stack at all. In this case, possible
+ listeners will be notified via
If the Undo manager is locked at the moment the method is called, the call will be ignored, and the Undo action +
If the Undo manager is locked at the moment the method is called, the call will be ignored, and the undo action will immediately be disposed, if applicable.
@throws ::com::sun::star::lang::IllegalArgumentException @@ -173,10 +173,8 @@ interface XUndoManagerIf one or more undo contexts are currently open, those will be implicit
-
@throws ::com::sun::star::util::InvalidStateException
- when the Undo stack is currently empty
+ when the undo stack is currently empty
@throws ::com::sun::star::lang::WrappedTargetException
if the invocation of
Note that the action must not necessarily be the new top element of the stack: In case there's an
open Undo context, 0
,
@@ -52,13 +52,13 @@ interface XUndoManagerListener : ::com::sun::star::lang::XEventListener
*/
void undoActionAdded( [in] UndoManagerEvent i_event );
- /** is called when the top-most action of the Undo stack has been undone.
+ /** is called when the top-most action of the undo stack has been undone.
@see XUndoManager::undo
*/
void actionUndone( [in] UndoManagerEvent i_event );
- /** is called when the top-most action of the Redo stack has been redone.
+ /** is called when the top-most action of the Redo stack has been re-applied.
@see XUndoManager::redo
*/
@@ -84,7 +84,7 @@ interface XUndoManagerListener : ::com::sun::star::lang::XEventListener
@see XUndoManager::enterUndoContext
*/
- void enteredUndoContext( [in] UndoManagerEvent i_event );
+ void enteredContext( [in] UndoManagerEvent i_event );
/** is called when a new hidden Undo context has been entered.
@@ -94,7 +94,7 @@ interface XUndoManagerListener : ::com::sun::star::lang::XEventListener
@see XUndoManager::enterUndoContext
*/
- void enteredHiddenUndoContext( [in] UndoManagerEvent i_event );
+ void enteredHiddenContext( [in] UndoManagerEvent i_event );
/** is called when an Undo context has been left.
@@ -104,9 +104,9 @@ interface XUndoManagerListener : ::com::sun::star::lang::XEventListener
@see XUndoManager::leaveUndoContext
@see leftHiddenUndocontext
- @see cancelledUndoContext
+ @see cancelledContext
*/
- void leftUndoContext( [in] UndoManagerEvent i_event );
+ void leftContext( [in] UndoManagerEvent i_event );
/** is calledn when a hidden Undo context has been left.
@@ -114,21 +114,21 @@ interface XUndoManagerListener : ::com::sun::star::lang::XEventListener
a title.
In such a case, the context which has just been left will not contribute to the Undo stack, but instead +
In such a case, the context which has just been left will not contribute to the undo stack, but instead be silently removed.
@see XUndoManager::leaveUndoContext - @see leftUndoContext - @see leftHiddenUndocontext + @see leftContext + @see leftHiddenContext */ - void cancelledUndoContext( [in] UndoManagerEvent i_event ); + void cancelledContext( [in] UndoManagerEvent i_event ); }; //================================================================================================================== -- cgit