Lines Matching refs:p
40 <p></p>
42 …<p>Changes to a document usually result in recording of information how to undo those changes, if …
44 … the changes they represent can be undo in the reverse order they have originally been applied.</p>
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>
51 …<p>For collecting multiple changes in a single undo action, so-called Undo contexts are provided. …
55 Undo contexts can be arbitrarily nested.</p>
58 … <p>Hidden Undo actions are those which in no observable way contribute to the undo stack. That is,
62 <member>leaveUndoContext</member>.</p>
66 <p>An Undo manager can be locked and unlocked, using the <member>XLockable::lock</member> and
68 enter or leave an Undo context, will be silently ignored.</p>
80 …<p><member scope="com::sun::star::container">XChild::setParent</member> is not supported, and will…
81 an <type scope="com::sun::star::lang">NoSupportException</type>.</p>
87 …<p>A new undo action will be added to the undo stack, with the title given as <code>i_title</code>…
90 separately undone or re-done.</p>
92 …<p>Each call to <code>enterUndoContext</code> must be paired by a call to <member>leaveUndoContext…
93 otherwise, the document's undo stack is left in an inconsistent state.</p>
95 … <p>Undo contexts can be nested, i.e. it is legitimate to call <code>enterUndoContext</code> and
96 …ndoContext</member> multiple times without calling <member>leaveUndoContext</member> inbetween.</p>
106 … <p>A hidden undo action does not, in any visible way, contribute to the undo stack. This means
113 action will not be listed.</p>
116 …<p>A new undo action will be added to the undo stack. As long as the context is not left, every un…
118 manager, not appear in any user interface, and cannot be separately undone or re-done.</p>
120 …<p>Each call to <code>enterHiddenUndoContext</code> must be paired by a call to <member>leaveUndoC…
121 otherwise, the document's undo stack is left in an inconsistent state.</p>
123 …<p>Undo contexts can be nested, i.e. it is legitimate to call <member>enterUndoContext</member> and
124 …nUndoContext</code> multiple times without calling <member>leaveUndoContext</member> inbetween.</p>
139 …<p>If no undo action has been added since the context has been opened, the context is not only lef…
141 listeners will be notified via <member>XUndoManagerListener::cancelledContext</member>.</p>
143 …<p>Otherwise, the undo context will be closed, and added to the Undo stack; the redo stack will be…
145 <member>XUndoManagerListener::leftHiddenContext</member></p>
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 …
163 interface.</p>
165 …<p>If the Undo manager is <a href="#locking">locked</a> at the moment the method is called, the ca…
166 will immediately be disposed, if applicable.</p>
178 <p>Effectively, invoking this method will
181 </ul></p>
203 <p>Effectively, invoking this method will
206 </ul></p>
275 … <p>All actions will be removed from both the Undo and the Redo stack. Actions which implement the
276 <type scope="com::sun::star::lang">XComponent</type> interface will be disposed.</p>
286 …<p>All actions will be removed from the Redo stack. Actions which implement the <type scope="com::…
287 interface will be disposed.</p>
297 <p>In particular, this method will
302 </ul></p>
304 …<p>Note that possible listeners will not get notifications for the single parts of the reset, i.e.…
307 … notified of the reset by calling their <member>XUndoManagerListener::resetAll</member> method.</p>