X-Git-Url: https://git.lyx.org/gitweb/?a=blobdiff_plain;f=src%2Fundo.h;h=9275e0e48cc2ed4cba96dc4fac8b3e9cd1d75381;hb=e94889a041628203c50b66b9a4add63210de6928;hp=e5060add608eb7c532a5724ef65447eddcc9a0e6;hpb=22590a98b36977c2257c66dc2d2a72741432d261;p=lyx.git diff --git a/src/undo.h b/src/undo.h index e5060add60..9275e0e48c 100644 --- a/src/undo.h +++ b/src/undo.h @@ -16,18 +16,41 @@ #ifndef UNDO_H #define UNDO_H -#include "ParagraphList_fwd.h" +#include "dociterator.h" +#include "ParagraphList.h" +#include "bufferparams.h" + #include "support/types.h" -class LCursor; +#include + +class BufferParams; class BufferView; +class LCursor; /** - * These are the elements put on the undo stack. Each object - * contains complete paragraphs and sufficient information - * to restore the state. - */ +These are the elements put on the undo stack. Each object contains complete +paragraphs from some cell and sufficient information to restore the cursor +state. + +The cell is given by a DocIterator pointing to this cell, the 'interesting' +range of paragraphs by counting them from begin and end of cell, +respectively. + +The cursor is also given as DocIterator and should point to some place in +the stored paragraph range. In case of math, we simply store the whole +cell, as there usually is just a simple paragraph in a cell. + +The idea is to store the contents of 'interesting' paragraphs in some +structure ('Undo') _before_ it is changed in some edit operation. +Obviously, the stored ranged should be as small as possible. However, it +there is a lower limit: The StableDocIterator pointing stored in the undo +class must be valid after the changes, too, as it will used as a pointer +where to insert the stored bits when performining undo. + +*/ + class Undo { public: /// This is used to combine consecutive undo recordings of the same kind. @@ -46,67 +69,67 @@ public: ATOMIC }; - /// constructor - Undo(undo_kind kind, int text, int index, - int first_par, int end_par, int cursor_par, int cursor_pos); - -public: - /// which kind of operation are we recording for? + /// Which kind of operation are we recording for? undo_kind kind; - /// hosting LyXText counted from buffer begin - int text; - /// cell in a tabular or similar - int index; - /// offset to the first paragraph in the paragraph list - int first_par; - /// offset to the last paragraph from the end of paragraph list - int end_par; - /// offset to the first paragraph in the paragraph list - int cursor_par; - /// the position of the cursor in the hosting paragraph - int cursor_pos; - /// the contents of the paragraphs saved + /// the position of the cursor + StableDocIterator cursor; + /// the position of the cell described + StableDocIterator cell; + /// counted from begin of cell + lyx::pit_type from; + /// complement to end of this cell + lyx::pit_type end; + /// the contents of the saved Paragraphs (for texted) ParagraphList pars; + /// the stringified contents of the saved MathArray (for mathed) + std::string array; + /// Only used in case of full backups + BufferParams bparams; + /// Only used in case of full backups + bool isFullBuffer; }; /// this will undo the last action - returns false if no undo possible -bool textUndo(BufferView &); +bool textUndo(BufferView & bv); /// this will redo the last undo - returns false if no redo possible -bool textRedo(BufferView &); +bool textRedo(BufferView & bv); /// makes sure the next operation will be stored void finishUndo(); -/// whilst undo is frozen, all actions do not get added to the undo stack -void freezeUndo(); - -/// track undos again -void unFreezeUndo(); - /** * Record undo information - call with the current cursor and the 'other * end' of the range of changed paragraphs. So we give an inclusive range. * This is called before you make the changes to the paragraph, and it * will record the original information of the paragraphs in the undo stack. + * + * FIXME: We need something to record undo in partial grids for mathed. + * Right now we use recordUndoInset if more than one cell is changed, + * but that puts the cursor in front of the inset after undo. We would need + * something like + * recordUndoGrid(LCursor & cur, Undo::undo_kind kind, idx_type from, idx_type to); + * and store the cell information in class Undo. */ -/// the common case: prepare undo for an arbitrary range +/// The general case: prepare undo for an arbitrary range. void recordUndo(LCursor & cur, Undo::undo_kind kind, - lyx::paroffset_type from, lyx::paroffset_type to); - -/// convienience: prepare undo for the range between 'from' and cursor. -void recordUndo(LCursor & cur, Undo::undo_kind kind, lyx::paroffset_type from); + lyx::pit_type from, lyx::pit_type to); -/// convienience: prepare undo for the single paragraph containing the cursor -void recordUndo(LCursor & cur, Undo::undo_kind kind); +/// Convenience: prepare undo for the range between 'from' and cursor. +void recordUndo(LCursor & cur, Undo::undo_kind kind, lyx::pit_type from); -/// convienience: prepare undo for the single paragraph containing the cursor -void recordUndoFullDocument(LCursor & cur); +/// Convenience: prepare undo for the single paragraph or cell +/// containing the cursor +void recordUndo(LCursor & cur, Undo::undo_kind kind = Undo::ATOMIC); +/// Convenience: prepare undo for the inset containing the cursor +void recordUndoInset(LCursor & cur, Undo::undo_kind kind = Undo::ATOMIC); +/// Convenience: prepare undo for the selected paragraphs +void recordUndoSelection(LCursor & cur, Undo::undo_kind kind = Undo::ATOMIC); -/// are we avoiding tracking undos currently? -extern bool undo_frozen; +/// Convenience: prepare undo for the whole buffer +void recordUndoFullDocument(BufferView * bv); #endif // UNDO_FUNCS_H