Tizen Native API  5.5
Smart Object Functions

Functions dealing with Evas smart objects (instances).

Smart objects are groupings of primitive Evas objects that behave as a cohesive group. For instance, a file manager icon may be a smart object composed of an image object, a text label and two rectangles that appear behind the image and text when the icon is selected. As a smart object, the normal Evas object API could be used on the icon object.

Besides that, generally smart objects implement a specific API, so that users interact with its own custom features. The API takes form of explicit exported functions one may call and smart callbacks.

Smart events and callbacks

Smart objects can elect events (smart events, from now on) occurring inside of them to be reported back to their users via callback functions (smart callbacks). This way, you can extend Evas' own object events. They are defined by an event string that identifies them uniquely. There's also a function prototype definition for the callback functions: #Evas_Smart_Cb.

When defining an Evas_Smart_Class, smart object implementors are strongly encouraged to properly set the Evas_Smart_Class::callbacks callbacks description array, so that the users of the smart object can have introspection on its events API at run time.

See some examples of this group of functions.

See also:
Smart Functions for class definitions.

Functions

void evas_smart_legacy_type_register (const char *type, const Efl_Class *klass)

Function Documentation

Evas_Object* evas_object_smart_add ( Evas e,
Evas_Smart *  s 
)

Get if the canvas is currently calculating smart objects.

Parameters:
[in]objThe object.
Returns:
true if currently calculating smart objects. Instantiates a new smart object described by s.
Parameters:
ethe canvas on which to add the object
sthe #Evas_Smart describing the smart object
Returns:
a new Evas_Object handle

This is the function one should use when defining the public function adding an instance of the new smart object to a given canvas. It will take care of setting all of its internals to work as they should, if the user set things properly, as seem on the EVAS_SMART_SUBCLASS_NEW, for example.

Since :
2.3
Examples:
evas-smart-interface.c, and evas-smart-object.c.
void evas_object_smart_callback_add ( Evas_Object obj,
const char *  event,
Evas_Smart_Cb  func,
const void *  data 
)

Add (register) a callback function to the smart event specified by event on the smart object obj.

Parameters:
obja smart object
eventthe event's name string
functhe callback function
datauser data to be passed to the callback function

Smart callbacks look very similar to Evas callbacks, but are implemented as smart object's custom ones.

This function adds a function callback to an smart object when the event named event occurs in it. The function is func.

In the event of a memory allocation error during addition of the callback to the object, evas_alloc_error() should be used to determine the nature of the error, if any, and the program should sensibly try and recover.

A smart callback function must have the ::Evas_Smart_Cb prototype definition. The first parameter (data) in this definition will have the same value passed to evas_object_smart_callback_add() as the data parameter, at runtime. The second parameter obj is a handle to the object on which the event occurred. The third parameter, event_info, is a pointer to data which is totally dependent on the smart object's implementation and semantic for the given event.

There is an infrastructure for introspection on smart objects' events (see evas_smart_callbacks_descriptions_get()), but no internal smart objects on Evas implement them yet.

See also:
Smart events and callbacks for more details.
evas_object_smart_callback_del()
Since :
2.3
Examples:
actionslider_example_01.c, bg_example_03.c, box_example_02.c, bubble_example_01.c, button_example_00.c, button_example_01.c, calendar_example_05.c, calendar_example_06.c, check_example_01.c, codegen_example.c, colorselector_example_01.c, combobox_example_01.c, ctxpopup_example_01.c, dayselector_example.c, diskselector_example_02.c, efl_thread_1.c, efl_thread_2.c, efl_thread_3.c, efl_thread_4.c, efl_thread_5.c, entry_example.c, evas-smart-interface.c, evas-smart-object.c, fileselector_button_example.c, fileselector_entry_example.c, fileselector_example.c, flip_example_01.c, flipselector_example.c, general_funcs_example.c, gengrid_example.c, genlist_example_02.c, genlist_example_04.c, genlist_example_05.c, glview_example_01.c, hover_example_01.c, hoversel_example_01.c, index_example_01.c, index_example_02.c, inwin_example.c, layout_example_01.c, layout_example_03.c, list_example_03.c, map_example_01.c, map_example_02.c, map_example_03.c, mapbuf_example.c, menu_example_01.c, naviframe_example.c, notify_example_01.c, panes_example.c, photocam_example_01.c, popup_example_01.c, popup_example_02.c, popup_example_03.c, prefs_example_01.c, prefs_example_02.c, prefs_example_03.c, progressbar_example.c, radio_example_01.c, slider_example.c, slideshow_example.c, spinner_example.c, theme_example_01.c, theme_example_02.c, thumb_example_01.c, transit_example_03.c, transit_example_04.c, web_example_02.c, and win_example.c.
void evas_object_smart_callback_call ( Evas_Object obj,
const char *  event,
void *  event_info 
)

Call a given smart callback on the smart object obj.

Parameters:
objthe smart object
eventthe event's name string
event_infopointer to an event specific struct or information to pass to the callback functions registered on this smart event

This should be called internally, from the smart object's own code, when some specific event has occurred and the implementor wants is to pertain to the object's events API (see Smart events and callbacks). The documentation for the smart object should include a list of possible events and what type of event_info to expect for each of them. Also, when defining an Evas_Smart_Class, smart object implementors are strongly encouraged to properly set the Evas_Smart_Class::callbacks callbacks description array, so that the users of the smart object can have introspection on its events API at run time.

Since :
2.3
Examples:
evas-smart-interface.c, and evas-smart-object.c.
void* evas_object_smart_callback_del ( Evas_Object obj,
const char *  event,
Evas_Smart_Cb  func 
)

Delete (unregister) a callback function from the smart event specified by event on the smart object obj.

Parameters:
obja smart object
eventthe event's name string
functhe callback function
Returns:
the data pointer

This function removes the first added smart callback on the object obj matching the event name event and the registered function pointer func. If the removal is successful it will also return the data pointer that was passed to evas_object_smart_callback_add() (that will be the same as the parameter) when the callback(s) was(were) added to the canvas. If not successful NULL will be returned.

See also:
evas_object_smart_callback_add() for more details.
Since :
2.3
void* evas_object_smart_callback_del_full ( Evas_Object obj,
const char *  event,
Evas_Smart_Cb  func,
const void *  data 
)

Delete (unregister) a callback function from the smart event specified by event on the smart object obj.

Parameters:
obja smart object
eventthe event's name string
functhe callback function
datathe data pointer that was passed to the callback
Returns:
the data pointer

This function removes the first added smart callback on the object obj matching the event name event, the registered function pointer func and the callback data pointer data. If the removal is successful it will also return the data pointer that was passed to evas_object_smart_callback_add() (that will be the same as the parameter) when the callback(s) was(were) added to the canvas. If not successful NULL will be returned. A common use would be to remove an exact match of a callback

See also:
evas_object_smart_callback_add() for more details.
Since (EFL) :
1.2
Note:
To delete all smart event callbacks which match type and func, use evas_object_smart_callback_del().
Since :
2.3
void evas_object_smart_callback_priority_add ( Evas_Object obj,
const char *  event,
Evas_Callback_Priority  priority,
Evas_Smart_Cb  func,
const void *  data 
)

Add (register) a callback function to the smart event specified by event on the smart object obj. Except for the priority field, it's exactly the same as evas_object_smart_callback_add

Parameters:
obja smart object
eventthe event's name string
priorityThe priority of the callback, lower values called first.
functhe callback function
datauser data to be passed to the callback function
See also:
evas_object_smart_callback_add
Since (EFL) :
1.1
Since :
3.0f(2.3.1)
void evas_object_smart_member_add ( Evas_Object obj,
Evas_Object smart_obj 
)

Set an Evas object as a member of a given smart object.

Parameters:
objThe member object
smart_objThe smart object

Members will automatically be stacked and layered together with the smart object. The various stacking functions will operate on members relative to the other members instead of the entire canvas, since they now live on an exclusive layer (see evas_object_stack_above(), for more details).

Any smart_obj object's specific implementation of the member_add() smart function will take place too, naturally.

See also:
evas_object_smart_member_del()
evas_object_smart_members_get()
Since :
2.3
Examples:
evas-smart-interface.c, and evas-smart-object.c.

Removes a member object from a given smart object.

Parameters:
objthe member object

This removes a member object from a smart object, if it was added to any. The object will still be on the canvas, but no longer associated with whichever smart object it was associated with.

See also:
evas_object_smart_member_add() for more details
evas_object_smart_members_get()
Since :
2.3
Examples:
evas-smart-interface.c, and evas-smart-object.c.
void evas_smart_legacy_type_register ( const char *  type,
const Efl_Class *  klass 
)

Registers an object type and its associated class. LEGACY MECHANISM SUPPORT.

This function is invoked in the class constructor of smart classes. It will add the type and the class into a hash table that will then be used to check the type of an object. This function has been implemented to support legacy mechanism that checks objects types by name. USE IT ONLY FOR LEGACY SUPPORT. Otherwise, it is HIGHLY recommended to use efl_isa.

Parameters:
typeThe type (name string) to add.
klassThe class to associate to the type.
See also:
efl_isa
Since :
3.0f(2.3.1)