forked from enlightenment/efl
parent
84f6ee1abf
commit
3d3f973105
|
@ -544,7 +544,7 @@ EAPI int ecore_thread_main_loop_end(void);
|
|||
* @endcode
|
||||
*
|
||||
* One very important thing to note here is the @c EVENT_TYPE, to register a
|
||||
* handler for an event you must know it's type before hand. Ecore provides
|
||||
* handler for an event you must know its type before hand. Ecore provides
|
||||
* the following events which are emitted in response to POSIX
|
||||
* signals(https://en.wikipedia.org/wiki/Signal_%28computing%29):
|
||||
* @li @b ECORE_EVENT_SIGNAL_USER
|
||||
|
|
|
@ -68,7 +68,7 @@
|
|||
|
||||
|
||||
/**
|
||||
* @defgroup Ecore_Con_Events_Group Events
|
||||
* @defgroup Ecore_Con_Events_Group Ecore Connection Events Functions
|
||||
*
|
||||
* @li ECORE_CON_CLIENT_ADD: Whenever a client connection is made to an
|
||||
* @c Ecore_Con_Server, an event of this type is emitted, allowing the
|
||||
|
@ -106,7 +106,7 @@
|
|||
*/
|
||||
|
||||
/**
|
||||
* @defgroup Ecore_Con_Buffer Buffering
|
||||
* @defgroup Ecore_Con_Buffer Ecore Connection Buffering
|
||||
*
|
||||
* As Ecore_Con works on an event driven design, as data arrives, events will
|
||||
* be produced containing the data that arrived. It is up to the user of
|
||||
|
|
Loading…
Reference in New Issue