Widgets can have different styles of look. These generic API's set styles of widgets, if they support them (and if the theme(s) do).

This example contemplates some of these functions.

Functions
Eina_Bool	elm_object_style_set (Evas_Object obj, const char style)
const char *	elm_object_style_get (const Evas_Object *obj)

Function Documentation

const char* elm_object_style_get ( const Evas_Object * obj )

Get the style used by the widget

This gets the style being used for that widget. Note that the string pointer is only valid as long as the object is valid and the style doesn't change.

Parameters:

obj	The Elementary widget to query for its style

Returns:: The style name used

See also:: elm_object_style_set()

Since :: 2.3

Eina_Bool elm_object_style_set	(	Evas_Object *	obj,
		const char *	style
	)

Set the style to used by a given widget

Parameters:

obj	The Elementary widget to style
style	The name of the style to use on it

Returns:: EINA_TRUE on success, EINA_FALSE otherwise

This sets the style (by name) that will define the appearance of a widget. Styles vary from widget to widget and may also be defined by other themes by means of extensions and overlays.

See also:: elm_theme_extension_add(); elm_theme_extension_del(); elm_theme_overlay_add(); elm_theme_overlay_del()

Since :: 2.3

Examples:: actionslider_example_01.c, bg_example_03.c, dayselector_example.c, frame_example_01.c, hover_example_01.c, inwin_example.c, label_example_01.c, mapbuf_example.c, progressbar_example.c, slideshow_example.c, spinner_example.c, theme_example_01.c, and transit_example_03.c.

Functions

Function Documentation