Lines Matching refs:be

44 … the changes they represent can be undo in the reverse order they have originally been applied.</p>
55     Undo contexts can be arbitrarily nested.</p>
61 …Hidden Undo actions can be created by calling <member>enterHiddenUndoContext</member>, following by
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>
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…
89 …it will not be directly accessible at the Undo manager, not appear in any user interface, and cann…
92 …<p>Each call to <code>enterUndoContext</code> must be paired by a call to <member>leaveUndoContext…
95 …    <p>Undo contexts can be nested, i.e. it is legitimate to call <code>enterUndoContext</code> and
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…
117 …added to the stack will be treated as sub action. This means it will not be directly accessible at…
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…
123 …<p>Undo contexts can be nested, i.e. it is legitimate to call <member>enterUndoContext</member> and
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…
144         and listeners will be notified via <member>XUndoManagerListener::leftContext</member> resp.
162 …<member>clearRedo</member>), it will be disposed, as long as it supports the <member scope="com::s…
165 …ef="#locking">locked</a> at the moment the method is called, the call will be ignored, and the und…
166         will immediately be disposed, if applicable.</p>
225     /** determines whether <member>undo</member> can reasonably be expected to succeed.
233     /** determines whether <member>redo</member> can reasonably be expected to succeed.
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>
305         will be no single <member>XUndoManagerListener::allActionsCleared</member>,
306 …<member>XUndoManagerListener::leftContext</member>, etc., notifications. Instead, listeners will be
311     /** adds a listener to be notified of changes in the Undo/Redo stacks.