Tizen Forums

Would you please go through this link ? I guess, it'll help you to understand the way of applying rotation to an object.

Hi, my question in that case was not how to rotate the lable (i have already posted it in this forum), was trying to understand why if i call that function in the _on_create_cb function, it return all 0s, but if the same function on the same object is called for example during a click-handler it return the correct values.

This is the code i was using:

Evas_Map *map = evas_map_new(4);
	evas_map_util_points_populate_from_object(map, vc->label1);
	evas_map_util_rotate(map, 180, x + (w / 2), y + (h / 2));
	evas_object_map_set(vc->label1, map);
	evas_object_map_enable_set(vc->label1, EINA_TRUE);
	elm_object_text_set(vc->label1, "Ci-ao");
	evas_map_free(map);

Taken directly from the example. 

The problem is  that if i try to print x,y,w,h they are all 0 if i'm in one of the following functions:

• static bool _on_create_cb(void *user_data)

• or the view_created event. 

Obviously this code snippet that should rotate the label it doesn't rotate it, and i'm wondering if the reason is the all 0s returned by the function. 

I created a new application and tried your code, and in that case it return the correct values. 

But i still don't understand why in my case doesn't. Consider that the UI is created using the UI-Builder (i don't know if this has some sort of impact).

And the same label that is not moved, nor resized, not touched in any way, the geometry is taken into the onclicked event, it return some values (that looks like correct values). 

But when in the function:

static bool _on_create_cb(void *user_data)

defined as a callback of the event create:

ui_app_lifecycle_callback_s cbs =
    {
		.create = _on_create_cb,
		.terminate = _on_terminate_cb,
		.pause = _on_pause_cb,
		.resume = _on_resume_cb,
		.app_control = _on_app_control_cb,
	};

It returns all 0s. But when i'm creating the layout programmatically it works fine (i think because i'm explicitly setting the geometry in that case. But declaring the layout programmatically is not very handy.