Lines Matching refs:stack
43 …ecords the information how to undo a single change. Undo actions are maintained in a stack, so that
47 …<p>Additionally, the Undo manager manages a Redo stack: Actions which are undone are moved from th…
48 stack, so it is possible to re-apply the changes to the document.</p>
52 …context is entered, all subsequently added Undo actions are not pushed onto the undo stack directl…
53 …he Undo context. Once the Undo context is left, a single undo action is pushed onto the undo stack,
58 … <p>Hidden Undo actions are those which in no observable way contribute to the undo stack. That is,
59 …any method retrieving information about the stack will behave as if the undo action does not exist…
87 …<p>A new undo action will be added to the undo stack, with the title given as <code>i_title</code>…
88 …as the context is not left, every undo action added to the stack will be treated as sub action. Th…
93 otherwise, the document's undo stack is left in an inconsistent state.</p>
106 … <p>A hidden undo action does not, in any visible way, contribute to the undo stack. This means
109 undo this action, and also undo the new top element of the stack.</li>
111 redo this action, and also redo the new top element of the stack.</li>
116 …<p>A new undo action will be added to the undo stack. As long as the context is not left, every un…
117 …added to the stack will be treated as sub action. This means it will not be directly accessible at…
121 otherwise, the document's undo stack is left in an inconsistent state.</p>
127 …if the undo stack is currently empty, in which case it is impossible to push a hidden undo action …
140 … but silently removed, and does not contribute to the undo stack at all. In this case, possible
143 …<p>Otherwise, the undo context will be closed, and added to the Undo stack; the redo stack will be…
156 /** adds the given undo action to the undo stack.
158 <p>The redo stack is cleared when a new action is pushed onto the undo stack.</p>
160 …<p>The Undo manager takes ownership of any actions pushed onto the undo stack. This means that if …
179 … <ul><li>invoke <member>XUndoAction::undo</member> on the top-most action of the undo stack</li>
180 <li>move this undo action from the undo stack to the redo stack</li>
184 if the undo stack is currently empty
190 …nvocation of <member>XUndoAction::undo</member> raised this exception. In this case, the undo stack
204 … <ul><li>invoke <member>XUndoAction::redo</member> on the top-most action of the redo stack</li>
205 <li>move this action from the redo stack to the undo stack</li>
209 when the Redo stack is currently empty
215 …nvocation of <member>XUndoAction::redo</member> raised this exception. In this case, the redo stack
228 … <FALSE/> if and only if the undo stack is currently empty, or there is an open and not-yet-closed
236 … <FALSE/> if and only if the redo stack is currently empty, or there is an open and not-yet-closed
241 /** returns the title of the top-most action on the undo stack
244 when the undo stack is currently empty
251 /** returns the title of the top-most action on the Redo stack
254 when the Redo stack is currently empty
260 /** returns the titles of all actions currently on the undo stack, from top to bottom
266 /** returns the titles of all actions currently on the Redo stack, from top to bottom
273 /** clears the undo and the redo stack.
275 … <p>All actions will be removed from both the Undo and the Redo stack. Actions which implement the
284 /** clears the redo stack.
286 …<p>All actions will be removed from the Redo stack. Actions which implement the <type scope="com::…
300 <li>clear the undo stack</li>
301 <li>clear the redo stack</li>