|
Tizen Native API
4.0
|
Functions that deal with messages.
Edje has two communication interfaces between code and theme. Signals and messages.
Edje messages are one of the communication interfaces between code and a given Edje object's theme. With messages, one can communicate values like strings, float numbers and integer numbers. Moreover, messages can be identified by integer numbers. See #Edje_Message_Type for the full list of message types.
- Note:
- Messages must be handled by scripts.
Functions | |
| void | edje_message_signal_process (void) |
| Processes all queued up edje messages. | |
Typedefs | |
| typedef void(* | Edje_Message_Handler_Cb )(void *data, Evas_Object *obj, Edje_Message_Type type, int id, void *msg) |
Typedef Documentation
| typedef void(* Edje_Message_Handler_Cb)(void *data, Evas_Object *obj, Edje_Message_Type type, int id, void *msg) |
Edje message handler callback functions's prototype definition. data will have the auxiliary data pointer set at the time the callback registration. obj will be a pointer the Edje object where the message comes from. type will identify the type of the given message and msg will be a pointer the message's contents, de facto, which depend on type.
Function Documentation
| void edje_message_signal_process | ( | void | ) |
Processes all queued up edje messages.
This function triggers the processing of messages addressed to any (alive) edje objects.
- Since :
- 2.3