/// Insets class Inset { public: /** This is not quite the correct place for this enum, but it is better than definitions.h. I think the correct would be to let each subclass of Inset declare its own enum code. Actually the notion of an Inset::Code should be avoided, but I am not sure how
this could be done in a cleaner way. */ enum Code { ///
NO_CODE, ///
TOC_CODE, // do these insets really need a code? (ale) ///
LOF_CODE, ///
LOT_CODE, ///
LOA_CODE, ///
QUOTE_CODE, ///
MARK_CODE, ///
REF_CODE, ///
URL_CODE, ///
HTMLURL_CODE, ///
SEPARATOR_CODE, ///
ENDING_CODE, ///
LABEL_CODE, ///
IGNORE_CODE, ///
ACCENT_CODE, ///
MATH_CODE, ///
INDEX_CODE, ///
INCLUDE_CODE, ///
GRAPHICS_CODE, ///
PARENT_CODE, ///
BIBTEX_CODE
};
/// virtual ~Inset(){}; /// virtualint Ascent(LyXFont const &font) const=0; /// virtualint Descent(LyXFont const &font) const=0; /// virtualint Width(LyXFont const& font) const=0; /// virtual LyXFont ConvertFont(LyXFont font); /// virtualvoid Draw(LyXFont font, LyXScreen &scr, int baseline, float &x)=0; /// //virtual void setBuffer(Buffer const&) {;} /// what appears in the minibuffer when opening virtualcharconst* EditMessage() {return _("Opened inset");} /// virtualvoid Edit(int, int); /// virtualunsignedchar Editable() const; /// virtualbool AutoDelete() const; /// virtualvoid Write(FILE *file)=0; /// virtualvoid Read(LyXLex &lex)=0; /** returns the number of rows (\n's) of generated tex code. fragile != 0 means, that the inset should take care about fragile commands by adding a \protect before.
*/ virtualint Latex(FILE *file, signedchar fragile)=0; virtualint Latex(LString &file, signedchar fragile)=0; /// virtualint Linuxdoc(LString &/*file*/) = 0; /// Updates needed features for this inset. virtualvoid Validate(LaTeXFeatures &features) const; /// virtualbool Deletable() const;
/// returns LyX code associated with the inset. Used for TOC, ...) virtual Inset::Code LyxCode() const = 0;
/// Get the label that appears at screen virtual LString getLabel(int) const { return LString();
}
/// used for autocorrection virtualbool IsEqual(Inset* /*other*/){ returnfalse;
}
/// virtual Inset* Clone()=0;
/// returns true to override begin and end inset in file virtualbool DirectWrite() const;
/// Returns true if the inset should be centered alone virtualbool Display() const { returnfalse; }
/// Changes the display state of the inset virtualvoid SetDisplay(bool) { } /// virtualint GetNumberOfLabels() const { return 0;
}
};
// Updatable Insets. These insets can be locked and receive // directly user interaction. Currently used only for mathed. // Note that all pure methods from Inset class are pure here too. // [Alejandro 080596]
/** Extracted from Matthias notes: * * An inset can simple call LockInset in it's edit call and *ONLY* * in it's edit call. * * Unlocking is either done by LyX or the inset itself with a * UnlockInset-call * * During the lock, all button and keyboard events will be modified * and send to the inset through the following inset-features. Note that * Inset::InsetUnlock will be called from inside UnlockInset. It is meant * to contain the code for restoring the menus and things like this. * * If a inset wishes any redraw and/or update it just has to call * UpdateInset(this). * * It's is completly irrelevant, where the inset is. UpdateInset will * find it in any paragraph in any buffer. * Of course the_locking_inset and the insets in the current paragraph/buffer * are checked first, so no performance problem should occur.
*/ class UpdatableInset: public Inset { public: /// virtual ~UpdatableInset() { }; /// virtualunsignedchar Editable() const;
/// may call ToggleLockedInsetCursor virtualvoid ToggleInsetCursor(); /// virtualvoid GetCursorPos(int&, int&) { } /// virtualvoid InsetButtonPress(int x, int y, int button); /// virtualvoid InsetButtonRelease(int x, int y, int button);
/// virtualvoid InsetKeyPress(XKeyEvent *ev); /// virtualvoid InsetMotionNotify(int x, int y, int state); /// virtualvoid InsetUnlock();
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung ist noch experimentell.