elementary_test -> Efl.Ui.Scroller -> move slider
Well this patch duplicate :
if (elm_widget_is_legacy(obj)) elm_interface_scrollable_hold_set(obj, EINA_TRUE); else efl_ui_scrollable_scroll_hold_set(obj, EINA_TRUE);
Putting that into an internal function helper would make this patch simpler and less error prone. Additional question, shouldn't we make elm_interface_scrollable_hold_set deprecated internally to make sure to not use it directly ? We can avoid the warning by having a #ifdef test that trigger a different function prototype (with and without deprecation) depending where it is included.
I don't know if there is difference between my code and code with internal function.
Also 'efl_ui_scrollable' and 'elm_interface_scrollable' exist separately.(elm_interface_scrollable.c and efl_ui_scroll_manager.c) Therefore legacy scrollable widgets use 'elm_interface_scrollable' and new efl widgets use 'efl_ui_scrollable'.
So I think to deprecating 'elm_interface_scrollable' is too much effort. (A lot of codes will be modified)
I think internal things could be arranged later.
After closing this task, @eagle001 needs to apply new efl_ui_scrollable to efl_ui_xxx classes.
(not for elm_xxx class which would be covered by elm_interface_scrollable. I don't think replacing elm_interface_scrollable to efl_ui_scrollable is urgent)
So, I hope to continue this discussion after applying current version of this patch.
Because it is giving several serious bugs now.
(For example, efl_ui_slider in vertical efl_ui_scroller is moving up and down - while changing its value by left and right moving.)
I wish you also agree with my opinion.