@zmike i think group_member_is is fine, its quite handy and support efl.canvas.group objects which do not force theire children to have them as render parent. Seems like it is somehow usefull.
seat_focus seems unused, do we want to remove it, its unclear to me what is actaully does. Additionally, it seems a bit off, that we have a list of seats *per* object.
I think event_animation can be a bit difficult and dangerous, you can see it with the implementation, two special cases for SHOW and HIDE. From a user POV this looks to me like i can go and add an animation to the POSITION_CHANGED event. However, you cannot, since the position will be moved. Not stopped by the animation, so to me this looks only usefull for hide and show. IMO it would be better to "copy" this functionality into efl_ui_stack.c (which is the only user of this). And remove this API and anim_* events from this object... What do you say @Jaehyun_Cho ?
I do not understand what is the problem. You want to rename Efl.Ui.Stack ? Why?
Where did this class go ? Can we close it as invalid ?
@cedric I think i found a problem, Efl.Ui.Widget_Factory, takes either a Efl.Ui.View or Efl.Ui.Widget class, which it uses to create the objects, but the objects need to be Efl.Gfx.Entity, should this be changed ?
Conceptionally this looks small and just fine, the docs are a bit weird to someone reading it the first time, but that does not block stabilization. @segfaultxavi what do you say ?
I guess this is the place where such things are used... :(
I cannot find any trace about "moved" event. Somebody knows about this ?