namespace: ewol::context::clipBoard


Description:



enum:

Synopsis:

  void                set       (enum ewol::context::clipBoard::clipboardListe _clipboardID,
const std::string & _data);
void request (enum ewol::context::clipBoard::clipboardListe _clipboardID);
void setSystem (enum ewol::context::clipBoard::clipboardListe _clipboardID,
const std::string & _data);
const std::string & get (enum ewol::context::clipBoard::clipboardListe _clipboardID);
void init (void );
void unInit (void );

Detail:

set

  void set (enum ewol::context::clipBoard::clipboardListe _clipboardID,
const std::string & _data);
set the string data on a specific clipboard. The Gui system is notify that the clipboard "SELECTION" and "COPY" are change


request

  void request (enum ewol::context::clipBoard::clipboardListe _clipboardID);
Call system to request the current clipboard.
Note: Due to some system that manage the clipboard request asynchronous (like X11) and ewol managing the system with only one thread, we need the call the system to send us the buffer, this is really ambigous, but the widget (who has focus) receive the notification of the arrival of this buffer id


setSystem

  void setSystem (enum ewol::context::clipBoard::clipboardListe _clipboardID,
const std::string & _data);
set the ewol internal buffer (no notification at the GUI). This fuction might be use by the Gui abstraction to set the buffer we receive. The end user must not use it.


get

  const std::string & get (enum ewol::context::clipBoard::clipboardListe _clipboardID);
get the ewol internal buffer of the curent clipboard. The end user can use it when he receive the event in the widget : @ref onEventClipboard == > we can nothe this function is the only one which permit it.
Note: if we call this fuction withoutcallin @ref ewol::context::clipBoard::Request, we only get the previous clipboard


init

  void init (void );
initialize the clipboard system (done by ewol)


unInit

  void unInit (void );
Un-Initialize the clipboard system (done by ewol)