How to create, initialize, manipulate and connect to signals of an Emotion object. More...
Typedefs | |
typedef struct _Emotion_Webcam | Emotion_Webcam |
Webcam description. | |
Functions | |
EAPI Eina_Bool | emotion_init (void) |
EAPI Eina_Bool | emotion_shutdown (void) |
EAPI Eina_Bool | emotion_object_video_handled_get (const Evas_Object *obj) |
EAPI Eina_Bool | emotion_object_audio_handled_get (const Evas_Object *obj) |
EAPI void | emotion_object_event_simple_send (Evas_Object *obj, Emotion_Event ev) |
EAPI int | emotion_object_audio_channel_count (const Evas_Object *obj) |
EAPI const char * | emotion_object_audio_channel_name_get (const Evas_Object *obj, int channel) |
EAPI void | emotion_object_audio_channel_set (Evas_Object *obj, int channel) |
EAPI int | emotion_object_audio_channel_get (const Evas_Object *obj) |
EAPI const char * | emotion_object_video_channel_name_get (const Evas_Object *obj, int channel) |
EAPI void | emotion_object_video_channel_set (Evas_Object *obj, int channel) |
EAPI int | emotion_object_video_channel_get (const Evas_Object *obj) |
EAPI void | emotion_object_spu_mute_set (Evas_Object *obj, Eina_Bool mute) |
EAPI Eina_Bool | emotion_object_spu_mute_get (const Evas_Object *obj) |
EAPI int | emotion_object_spu_channel_count (const Evas_Object *obj) |
EAPI const char * | emotion_object_spu_channel_name_get (const Evas_Object *obj, int channel) |
EAPI void | emotion_object_spu_channel_set (Evas_Object *obj, int channel) |
EAPI int | emotion_object_spu_channel_get (const Evas_Object *obj) |
EAPI int | emotion_object_chapter_count (const Evas_Object *obj) |
EAPI void | emotion_object_chapter_set (Evas_Object *obj, int chapter) |
EAPI int | emotion_object_chapter_get (const Evas_Object *obj) |
EAPI const char * | emotion_object_chapter_name_get (const Evas_Object *obj, int chapter) |
EAPI void | emotion_object_eject (Evas_Object *obj) |
EAPI const char * | emotion_object_ref_file_get (const Evas_Object *obj) |
EAPI int | emotion_object_ref_num_get (const Evas_Object *obj) |
EAPI int | emotion_object_spu_button_count_get (const Evas_Object *obj) |
EAPI int | emotion_object_spu_button_get (const Evas_Object *obj) |
EAPI Eina_Bool | emotion_object_extension_may_play_fast_get (const char *file) |
Do we have a chance to play that file. More... | |
EAPI Eina_Bool | emotion_object_extension_may_play_get (const char *file) |
Do we have a chance to play that file. More... | |
EAPI Evas_Object * | emotion_object_image_get (const Evas_Object *obj) |
Get the actual image object that contains the pixels of the video stream. More... | |
Variables | |
EAPI int | EMOTION_WEBCAM_UPDATE |
Ecore_Event triggered when a new webcam is plugged or unplugged. | |
EAPI int | EMOTION_WEBCAM_ADD |
Ecore_Event triggered when a new webcam is plugged in. More... | |
EAPI int | EMOTION_WEBCAM_DEL |
Ecore_Event triggered when a webcam is unplugged. More... | |
How to create, initialize, manipulate and connect to signals of an Emotion object.
Emotion provides an Evas smart object that allows to play, control and display a video or audio file. The API is synchronous but not everything happens immediately. There are also some signals to report changed states.
Basically, once the object is created and initialized, a file will be set to it, and then it can be resized, moved, and controlled by other Evas object functions.
However, the decoding of the music and video occurs not in the Ecore main loop, but usually in another thread (this depends on the module being used). The synchronization between this other thread and the main loop not visible to the end user of the library. The user can just register callbacks to the available signals to receive information about the changed states, and can call other functions from the API to request more changes on the current loaded file.
There will be a delay between an API being called and it being really executed, since this request will be done in the main thread, and it needs to be sent to the decoding thread. For this reason, always call functions like emotion_object_size_get() or emotion_object_length_get() after some signal being sent, like "playback_started" or "open_done". This example demonstrates this behavior.
The Evas_Object returned by emotion_object_add() has a number of signals that can be listened to using evas' smart callbacks mechanism. All signals have NULL as event info. The following is a list of interesting signals:
The following examples exemplify the emotion usage. There's also the emotion_test binary that is distributed with this library and cover the entire API, but since it is too long and repetitive to be explained, its code is just displayed as another example.
Do we have a chance to play that file.
file | A stringshared filename that we want to know if Emotion can play. |
This just actually look at the extention of the file, it doesn't check the mime-type nor if the file is actually sane. So this is just an hint for your application.
Do we have a chance to play that file.
file | A filename that we want to know if Emotion can play. |
This just actually look at the extention of the file, it doesn't check the mime-type nor if the file is actually sane. So this is just an hint for your application.
EAPI Evas_Object* emotion_object_image_get | ( | const Evas_Object * | obj | ) |
Get the actual image object that contains the pixels of the video stream.
obj | The object which the query is being ran on. |
This function is usefull when you want to get a direct access to the pixels.
References EAPI, and evas_object_smart_data_get().
EAPI int EMOTION_WEBCAM_ADD |
Ecore_Event triggered when a new webcam is plugged in.
EAPI int EMOTION_WEBCAM_DEL |
Ecore_Event triggered when a webcam is unplugged.