enlightenment/efl
enlightenment
/
efl
8
7
Fork 14
Code Issues 13 Pull Requests 1 Projects Releases Wiki Activity

fix typos in APIs doc

This commit is contained in:
Amitesh Singh 2015-09-19 09:13:09 +05:30
parent ef530149b6
commit e96771e383
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
legacy/elementary/src/lib/elm_app_server.eo
View File

@ -53,7 +53,7 @@ class Elm_App_Server (Eo.Base)
legacy: null;
params {
@in packageid: const(char)*; [[package of application]]
@in create_view_cb: Elm_App_Server_Create_View_Cb; [[callback to be called when user whants to open some application view]]
@in create_view_cb: Elm_App_Server_Create_View_Cb; [[callback to be called when user wants to open some application view]]
}
}
close_all {

4
legacy/elementary/src/lib/elm_widget_item.eo
View File

@ -385,7 +385,7 @@ class Elm.Widget_Item(Eo.Base, Elm_Interface_Atspi_Accessible,
[[This returns track object of the item.
Note: This gets a rectangle object that represents the object item's internal
object. If you wanna check the geometry, visibility of the item, you
object. If you want to check the geometry, visibility of the item, you
can call the evas apis such as evas_object_geometry_get(),
evas_object_visible_get() to the track object. Note that all of the
widget items may/may not have the internal object so this api may
@ -424,7 +424,7 @@ class Elm.Widget_Item(Eo.Base, Elm_Interface_Atspi_Accessible,
Note: This gets the reference count for the track object. Whenever you call
the @.track, the reference count will be increased by
one. Likely the referece count will be decreased again when you call
one. Likely the reference count will be decreased again when you call
the @.untrack. Unless the reference count reaches to
zero, the track object won't be deleted. So please be sure to call
@.untrack() paired to the elm_object_item_track call