class Efl.Ui.Scroller @beta
|Open||None||T7510 evaluate stabilization potential of efl.ui classes and dependencies|
|Resolved||None||T7921 enum Efl.Ui.Scroll_Block|
|Resolved||None||T7923 enum Efl.Ui.Scrollbar_Mode|
|Resolved||zmike||T7924 enum Efl.Ui.Scrollbar_Direction|
|Open||None||T7912 enum Efl.Input.Object_Pointer_Mode|
|Open||None||T7913 function Efl.Ui.Selection_Data_Ready|
|Open||None||T7914 struct Efl.Ui.Selection_Changed|
|Open||None||T7915 enum Efl.Ui.Selection_Type|
|Open||None||T7916 enum Efl.Ui.Selection_Format|
|Open||None||T7917 enum Efl.Ui.Activate|
|Resolved||None||T7919 enum Efl.Orient|
|Resolved||zmike||T8051 Indicators on the scrollbar do not work|
|Resolved||None||T8052 Mouse Wheel interaction|
I cannot catch well your point.
Legacy elm_scroller is something that can contains everything what application wants - and this efl_ui_scroller is an alternative for that.
So, I think that efl_ui_scroller would be used a lot from application directly.
Let me know if I am not understanding well about your point.
Scroller itself is a widget container. It holds other widgets and scrolls them.
There is also the ability to implement scrolling directly inside widgets, for example in lists. A list widget does not need to be inside a scroller because it can scroll. So for example, if you have a series of images packed into a box widget, you would put the box into a scroller to provide scrolling since a box cannot scroll, and you would need this class.
I am just making sure that there is a direct demand to have this class stable in this release.