/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
/*
* This file is part of the LibreOffice project.
*
* This Source Code Form is subject to the terms of the Mozilla Public
* License, v. 2.0. If a copy of the MPL was not distributed with this
* file, You can obtain one at http://mozilla.org/MPL/2.0/.
*
* This file incorporates work covered by the following license notice:
*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed
* with this work for additional information regarding copyright
* ownership. The ASF licenses this file to you under the Apache
* License, Version 2.0 (the "License"); you may not use this file
* except in compliance with the License. You may obtain a copy of
* the License at http://www.apache.org/licenses/LICENSE-2.0 .
*/
#ifndef __com_sun_star_document_XUndoManager_idl__
#define __com_sun_star_document_XUndoManager_idl__
#include 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
the changes they represent can be undo in the reverse order they have originally been applied. Additionally, the Undo manager manages a Redo stack: Actions which are undone are moved from the Undo to the Redo
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,
which comprises all those single Undo actions. 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 undo() respectively redo() will include those actions. An Undo manager can be locked and unlocked, using the XLockable::lock() and
XLockable::unlock() methods. When it is locked, then every attempt to add an undo action, or to
enter or leave an Undo context, will be silently ignored. com::sun::star::container::XChild::setParent() is not supported, and will throw
a com::sun::star::lang::NoSupportException. A new undo action will be added to the undo stack, with the title given as Each call to Undo contexts can be nested, i.e. it is legitimate to call A hidden undo action does not, in any visible way, contribute to the undo stack. This means
that
Undo
Redo
Undo contexts
Undo contexts can be arbitrarily nested.Hidden Undo actions
Hidden Undo actions can be created by calling enterHiddenUndoContext(), following by
leaveUndoContext().Locking
iTitle
. As long
as the context is not left, every undo action added to the stack will be treated as sub action. This means
it will not be directly accessible at the Undo manager, not appear in any user interface, and cannot be
separately undone or re-done.enterUndoContext
must be paired by a call to leaveUndoContext(),
otherwise, the document's undo stack is left in an inconsistent state.enterUndoContext
and
enterHiddenUndoContext() multiple times without calling leaveUndoContext() inbetween.
A new undo action will be added to the undo stack. As long as the context is not left, every undo action added to the stack will be treated as sub action. This means it will not be directly accessible at the undo manager, not appear in any user interface, and cannot be separately undone or re-done.
Each call to enterHiddenUndoContext
must be paired by a call to leaveUndoContext(),
otherwise, the document's undo stack is left in an inconsistent state.
Undo contexts can be nested, i.e. it is legitimate to call enterUndoContext() and
enterHiddenUndoContext
multiple times without calling leaveUndoContext() inbetween.
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 XUndoManagerListener::cancelledContext().
Otherwise, the undo context will be closed, and added to the Undo stack; the redo stack will be cleared, and listeners will be notified via XUndoManagerListener::leftContext() resp. XUndoManagerListener::leftHiddenContext()
@throws ::com::sun::star::util::InvalidStateException if no undo context is currently open. @see enterUndoContext @see enterHiddenUndoContext */ void leaveUndoContext() raises( ::com::sun::star::util::InvalidStateException ); /** adds the given undo action to the undo stack.The redo stack is cleared when a new action is pushed onto the undo stack.
The Undo manager takes ownership of any actions pushed onto the undo stack. This means that if the action is finally removed from the Undo manager's control (e.g. by calling clear() resp. clearRedo()), it will be disposed, as long as it supports the com::sun::star::lang::XComponent interface.
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 if the given undo action is `NULL`. */ void addUndoAction( [in] XUndoAction iAction ) raises( ::com::sun::star::lang::IllegalArgumentException ); /** reverts the most recent action on the document.Effectively, invoking this method will
Effectively, invoking this method will
All actions will be removed from both the Undo and the Redo stack. Actions which implement the com::sun::star::lang::XComponent interface will be disposed.
@throws UndoContextNotClosedException if the method is invoked while an undo context is still open */ void clear() raises( ::com::sun::star::document::UndoContextNotClosedException ); /** clears the redo stack.All actions will be removed from the Redo stack. Actions which implement the com::sun::star::lang::XComponent interface will be disposed.
@throws UndoContextNotClosedException if the method is invoked while an undo context is still open */ void clearRedo() raises( ::com::sun::star::document::UndoContextNotClosedException ); /** resets the Undo managerIn particular, this method will
Note that possible listeners will not get notifications for the single parts of the reset, i.e. there will be no single XUndoManagerListener::allActionsCleared(), XUndoManagerListener::leftContext(), etc., notifications. Instead, listeners will be notified of the reset by calling their XUndoManagerListener::resetAll() method.
*/ void reset(); /** adds a listener to be notified of changes in the Undo/Redo stacks. */ void addUndoManagerListener( [in] XUndoManagerListener iListener ); /** removes a previously added listener */ void removeUndoManagerListener( [in] XUndoManagerListener iListener ); }; }; }; }; }; #endif /* vim:set shiftwidth=4 softtabstop=4 expandtab: */