lyx_mirror/src/lyxfunc.h
Abdelrazak Younes 311ac9b192 This is the continuation of my BufferView/LyXView cleanup. This commit replaces BufferView->LyXView->getDialogs().[show(), update()] with BufferView signal emissions.
The associated WorkArea is then responsible to connect these signals to its LyXView parent.

* BufferView:
  - showDialog, showDialogWithData, showInsetDialog: new boost signals

* LyXView:
  - connectBufferView(), disconnectBufferView(): new method in charge of the connection/disconnection of the above signal to associate private methods (showDialog(), etc).

* WorkArea
  - setBufferView(): will connect/disconnect the BufferView to its LyXView parent.


git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@15068 a592a061-630c-0410-9148-cb99ea01b6c8
2006-09-19 13:36:20 +00:00

116 lines
2.8 KiB
C++

// -*- C++ -*-
/**
* \file lyxfunc.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 Jean-Marc Lasgouttes
* \author John Levon
* \author André Pönitz
*
* Full author contact details are available in file CREDITS.
*/
#ifndef LYXFUNC_H
#define LYXFUNC_H
#include "kbsequence.h"
#include "lfuns.h"
#include "support/docstring.h"
#include <boost/shared_ptr.hpp>
#include <boost/signals/trackable.hpp>
class BufferView;
class FuncRequest;
class FuncStatus;
class LyXKeySym;
class LyXText;
class LyXView;
/** This class encapsulates all the LyX command operations.
This is the class of the LyX's "high level event handler".
Every user command is processed here, either invocated from
keyboard or from the GUI. All GUI objects, including buttons and
menus should use this class and never call kernel functions directly.
*/
class LyXFunc : public boost::signals::trackable {
public:
///
explicit LyXFunc(LyXView * lv = 0);
/// LyX dispatcher, executes lyx actions.
void dispatch(FuncRequest const &);
/// return the status bar state string
std::string const viewStatusMessage();
///
void processKeySym(LyXKeySymPtr key, key_modifier::state state);
///
FuncStatus getStatus(FuncRequest const & action) const;
/// The last key was meta
bool wasMetaKey() const;
/// True if lyxfunc reports an error
bool errorStat() const { return errorstat; }
/// Buffer to store result messages
void setMessage(lyx::docstring const & m) const;
/// Buffer to store result messages
void setErrorMessage(lyx::docstring const &) const;
/// Buffer to store result messages
lyx::docstring const getMessage() const { return dispatch_buffer; }
/// Handle a accented char key sequence
void handleKeyFunc(kb_action action);
private:
///
BufferView * view() const;
///
LyXView * owner;
/// the last character added to the key sequence, in ISO encoded form
lyx::char_type encoded_last_key;
///
kb_sequence keyseq;
///
kb_sequence cancel_meta_seq;
///
key_modifier::state meta_fake_bit;
///
void setupLocalKeymap();
/// Error status, only Dispatch can change this flag
mutable bool errorstat;
/** Buffer to store messages and result data. Is there a
good reason to have this one as static in Dispatch? (Ale)
*/
mutable lyx::docstring dispatch_buffer;
/// send a post-dispatch status message
void sendDispatchMessage(lyx::docstring const & msg,
FuncRequest const & ev);
// I think the following should be moved to BufferView. (Asger)
///
void menuNew(std::string const & argument, bool fromTemplate);
///
void open(std::string const &);
///
void doImport(std::string const &);
///
void closeBuffer();
///
bool ensureBufferClean(BufferView * bv);
};
#endif