fix build error

Is it OK if this patch is submitted?

thank you! :)

Apply clipper not to cause tests fail with setting data "_elm_leaveme".

Oh! I missed plain;; thank you!

add code for spotlight manager plain, too

As this patch describes, now group_member_add() of efl_ui_widget set color_set() manually. This causes packed rectangle's color change.

thank you for the update!

How about using global variable static unsigned int ts ?

static unsigned int ts = 0; //global variable in suite_helpers.c

Because the timestamp of each function begins with 0 so timestamp 0 is used in the functions at the same time.
e.g.

//In test code
drag_object(...); //timestamp 0 is used with evas_event_feed_mouse_move
wheel_object_at(...); //timestamp 0 is used with evas_event_feed_mouse_move

There are many patches related to gesture. (D11052, D11053, ...)
Therefore, to avoid conflict to the above patches, this patch should not be merged until either those patches are merged or abandoned.

This patch is basically the same with D11108.

This patch suggests using "Animation" as a postfix of animation class names.
e.g. Efl.Canvas.Animation_Alpha -> Efl.Canvas.Alpha_Animation

update description about the value is_duration_set

I agree with your opinion! Power_Interpolator :)

It seems that GetEoOps() can be called multiple times if inherited classes' instances are created.

It seems that it is required to consider that only specific part classes generate extension classes (not all part classes) as @woohyun mentioned. (e.g. Efl.Ui.Layout_Part_Text, ...)

Thank you for your reply! Now I understand your point and I agree with you.

• NOW : radius_get { } for Efl.Canvas.Gesture_Zoom
• TODO : @property radius { get { } } for Efl.Canvas.Gesture_Zoom

Based on the above discussion, how about the followings in efl_model.eo?

child,added : Efl.Model_Child_Event;
child,removed : Efl.Model_Child_Event;
children,added : Efl.Model_Children_Event;
children,removed : Efl.Model_Children_Event;

This class was added based on ELM_TRANSIT_TWEEN_MODE_DIVISOR_INTERP, ECORE_POS_MAP_DIVISOR_INTERP and ECORE_POS_MAP_DIVISOR_INTERP.

Their fields should be read-only properties instead of methods. This is more natural for bindings.

Do you mean that EITHER Efl.Canvas.Gesture provides read-only properties OR Efl.Canvas.Gesture's setter methods / writable properties should not be public?

In D10929#205857, @YOhoho wrote:

Also, This patch will fix CA1052(T8398).

It's nice! :) Thank you!

Is it possible to apply this scheme to other data types? (e.g. enum in .eo)

Thank you for the patch :)

Thank you!

Thank you for this patch!

@bu5hm4n
I also agree with @segfaultxavi and you. Let's keep push and pop in the place~ Thank you :)

Unit test is added. Thank you :)

I understand your point that non-zero value would be more useful as default duration than 0.
So I restored the default duration of animation in D10812.

fixed vector if speed < 0.0.
modified duration check codes to support duration 0.

I don't mind the function setting default duration value :)
It may be useful to someone who wants to set the same duration multiple times~
I simply think that we need to let animation support duration 0 as well.

updates task refs

I think if duration is 0, then the final state of animation is applied immediately. (It seems that current animation logic does not support duration 0)

In T7991#147502, @bu5hm4n wrote:

It is theoretically possible. However, the implementation in Efl.Ui.Spotlight.Container is *way* more performent, and does not need event subscriptions at all ..., its a matter or priority i guess. What if we call them "animated_insert" and "animated_remove", and move the name push and pop to Stack, where we can also ensure that @segfaultxavi's concerns are met ?

Thank you for your reply :)

@bu5hm4n @segfaultxavi
Thank you very much :)