forked from enlightenment/efl
evas: fix typos in documentation
This commit is contained in:
parent
d889da6b12
commit
83beb559e9
|
@ -929,7 +929,7 @@ EAPI int evas_async_events_process(void);
|
|||
* @param event_info Information about the event.
|
||||
* @param func The callback function pointer.
|
||||
*
|
||||
* @return EINA_FALSE if an error occured, EINA_TRUE otherwise.
|
||||
* @return EINA_FALSE if an error occurred, EINA_TRUE otherwise.
|
||||
*
|
||||
* This is the way, for a routine running outside evas' main thread,
|
||||
* to report an asynchronous event. A callback function is informed,
|
||||
|
@ -1225,7 +1225,7 @@ EAPI void evas_render_updates_free(Eina_List *updates);
|
|||
* part of the canvas @p e will automatically be deleted when the canvas
|
||||
* is freed.
|
||||
*
|
||||
* @return the device node created or NULL if an error occured.
|
||||
* @return the device node created or NULL if an error occurred.
|
||||
*
|
||||
* @see evas_device_del
|
||||
* @since 1.8
|
||||
|
@ -1433,7 +1433,7 @@ EAPI Evas_Device_Class evas_device_class_get(const Evas_Device *dev);
|
|||
* @param dev The device to modify
|
||||
* @param clas The sub-class to set
|
||||
*
|
||||
* This sets the sub-class of a device whihc gives much more detailed usage
|
||||
* This sets the sub-class of a device which gives much more detailed usage
|
||||
* within a broader category.
|
||||
*
|
||||
* @since 1.8
|
||||
|
@ -5414,7 +5414,7 @@ EAPI const Eina_List *evas_font_path_global_list(void) EINA_WARN_UNUSED_R
|
|||
|
||||
/**
|
||||
* Reinitialize FontConfig. If FontConfig has to be reinitialized
|
||||
* according to changes of system enviroments(ex. Changing font config files), it will be useful.
|
||||
* according to changes of system environments(ex. Changing font config files), it will be useful.
|
||||
*
|
||||
* @ingroup Evas_Font_Path_Group
|
||||
* @since 1.14
|
||||
|
|
|
@ -189,7 +189,7 @@ EAPI extern const Eo_Event_Description _EVAS_CANVAS_EVENT_VIEWPORT_RESIZE;
|
|||
* to connect the scene with an evas image object so that the scene is rendered
|
||||
* on that image object.
|
||||
*
|
||||
* Contruction of a 3D scene is process of locating desired cameras, lights and
|
||||
* Construction of a 3D scene is process of locating desired cameras, lights and
|
||||
* meshes in the scene. Typically the scene is structured with some hierarchical
|
||||
* data structure. Evas 3D support n-ary tree structure for describing the
|
||||
* scene. Node is used to build the tree representation of the scene. Other
|
||||
|
@ -271,7 +271,7 @@ EAPI extern const Eo_Event_Description _EVAS_CANVAS_EVENT_VIEWPORT_RESIZE;
|
|||
* camera on a node. If one wants to locate several cameras having same
|
||||
* properties, instead of creating multiple cameras, just create one camera and
|
||||
* multiple nodes containing the camera and locate them at each desired position
|
||||
* and direction. Just for convinience, use evas_canvas3d_node_position_set() to move
|
||||
* and direction. Just for convenience, use evas_canvas3d_node_position_set() to move
|
||||
* the camera to desired position and use evas_canvas3d_node_look_at_set() to adjust
|
||||
* the viewing direction of the camera.
|
||||
*/
|
||||
|
|
|
@ -2046,7 +2046,7 @@ EAPI Efl_Gfx_Join evas_vg_shape_stroke_join_get(Eo *obj);
|
|||
*
|
||||
* Sets the join style to be used for stroking the path.
|
||||
* The join style will be used for joining the two line segment
|
||||
* while stroking teh path.
|
||||
* while stroking the path.
|
||||
*
|
||||
* @see Efl_Gfx_Join
|
||||
* @since 1.14
|
||||
|
|
Loading…
Reference in New Issue