Now owner widget (elm_widget) is just used to listen for theme changes and create/destroy the tooltip data. The actual mouse events operates on all Evas_Object and is the one where tooltip data is actually stored. The public API is basically the same, just the event_info is now NULL to avoid confusion. The internal API introduces elm_object_sub_tooltip_content_cb_set() and as the first parameter the eventarea. While this may be confusing, as the second parameter is the actual elementary object, it is the one that all other calls receive, like elm_object_tooltip_hide() or elm_object_tooltip_unset(), thus it does make sense to have such order. Also internal API, elm_widget_item_tooltip_* functions were added. They are a variation of the widget API to handle its items, as such the func() gets one more parameter: item, and the del_cb() gets the item as event_info (that's why the public widget version got event_info always NULL, to not confuse with this one!) Widgets with items that makes sense to have tooltips got extra API: * toolbar * list * gengrid * genlist SVN revision: 52173 |
||
---|---|---|
.. | ||
config | ||
data | ||
debian | ||
doc | ||
m4 | ||
src | ||
.gitignore | ||
AUTHORS | ||
COPYING | ||
ChangeLog | ||
INSTALL | ||
Makefile.am | ||
NEWS | ||
README | ||
autogen.sh | ||
configure.ac | ||
elementary.pc.in | ||
elementary.spec.in |
README
Elementary - a basic widget set that is easy to use based on EFL for mobile touch-screen devices.