lyx_mirror/src/cursor_slice.h
Martin Vermeer 883decc7da Fix the assert when copying rows or columns in math.
git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@10114 a592a061-630c-0410-9148-cb99ea01b6c8
2005-06-30 18:02:39 +00:00

170 lines
4.7 KiB
C++

// -*- C++ -*-
/**
* \file cursor_slice.h
* This file is part of LyX, the document processor.
* Licence details can be found in the file COPYING.
*
* \author Lars Gullik Bjønnes
* \author Matthias Ettrich
* \author John Levon
* \author André Pönitz
* \author Dekel Tsur
* \author Jürgen Vigna
*
* Full author contact details are available in file CREDITS.
*/
#ifndef CURSORSLICE_H
#define CURSORSLICE_H
#include "support/types.h"
#include <cstddef>
#include <iosfwd>
class BufferView;
class InsetBase;
class MathInset;
class MathArray;
class LyXText;
class Paragraph;
class UpdatableInset;
/// This encapsulates a single slice of a document iterator as used e.g.
/// for cursors.
// After IU, the distinction of MathInset and UpdatableInset as well as
// that of MathArray and LyXText should vanish. They are conceptually the
// same (now...)
class CursorSlice {
public:
/// type for cell number in inset
typedef size_t idx_type;
/// type for paragraph numbers positions within a cell
typedef lyx::pit_type pit_type;
/// type for cursor positions within a cell
typedef lyx::pos_type pos_type;
/// type for row indices
typedef size_t row_type;
/// type for col indices
typedef size_t col_type;
///
CursorSlice();
///
explicit CursorSlice(InsetBase &);
/// the current inset
InsetBase & inset() const { return *inset_; }
/// return the cell this cursor is in
idx_type idx() const { return idx_; }
/// return the cell this cursor is in
idx_type & idx() { return idx_; }
/// Save current cursor idx as row, col
void idxSave() { col_ = idx_ % ncols(); row_ = idx_ / ncols(); }
/// update idx to correspond to row, col
void idxLoad() { idx_ = col_ + ncols() * row_; }
/// return the last cell in this inset
idx_type lastidx() const { return nargs() - 1; }
/// return the offset of the paragraph this cursor is in
pit_type pit() const { return pit_; }
/// set the offset of the paragraph this cursor is in
pit_type & pit() { return pit_; }
/// increments the paragraph this cursor is in
void incrementPar();
/// decrements the paragraph this cursor is in
void decrementPar();
/// return the position within the paragraph
pos_type pos() const { return pos_; }
/// return the position within the paragraph
pos_type & pos() { return pos_; }
/// return the last position within the paragraph
pos_type lastpos() const;
/// return the number of embedded cells
size_t nargs() const;
/// return the number of columns
size_t ncols() const;
/// return the number of rows
size_t nrows() const;
/// return the grid row of the current cell
row_type row() const;
/// return the grid column of the current cell
col_type col() const;
///
/// texted specific stuff
///
/// see comment for the member
bool boundary() const { return boundary_; }
/// see comment for the member
bool & boundary() { return boundary_; }
///
LyXText * text();
///
LyXText const * text() const;
///
UpdatableInset * asUpdatableInset() const;
///
Paragraph & paragraph();
///
Paragraph const & paragraph() const;
///
/// mathed specific stuff
///
/// returns cell corresponding to this position
MathArray & cell() const;
///
MathInset * asMathInset() const;
///
friend std::ostream & operator<<(std::ostream &, CursorSlice const &);
public:
/// pointer to 'owning' inset. This is some kind of cache.
InsetBase * inset_;
private:
/// cell index of a position in this inset
idx_type idx_;
/// row position in inset
row_type row_;
/// column position in inset
col_type col_;
/// paragraph in this cell (used by texted)
pit_type pit_;
/// true of 'pit' was properly initialized
bool pit_valid_;
/// position in this cell
pos_type pos_;
/**
* When the cursor position is i, is the cursor is after the i-th char
* or before the i+1-th char ? Normally, these two interpretations are
* equivalent, except when the fonts of the i-th and i+1-th char
* differ.
* We use boundary_ to distinguish between the two options:
* If boundary_=true, then the cursor is after the i-th char
* and if boundary_=false, then the cursor is before the i+1-th char.
*
* We currently use the boundary only when the language direction of
* the i-th char is different than the one of the i+1-th char.
* In this case it is important to distinguish between the two
* cursor interpretations, in order to give a reasonable behavior to
* the user.
*/
bool boundary_;
};
/// test for equality
bool operator==(CursorSlice const &, CursorSlice const &);
/// test for inequality
bool operator!=(CursorSlice const &, CursorSlice const &);
/// test for order
bool operator<(CursorSlice const &, CursorSlice const &);
/// test for order
bool operator>(CursorSlice const &, CursorSlice const &);
/// test for order
bool operator<=(CursorSlice const &, CursorSlice const &);
#endif