| |interface Efl.Ui.Scrollable_Interactive @beta |├ (P) content_pos |├ (P) content_size |├ (P) viewport_geometry |├ (P) bounce_enabled |├ (P) scroll_freeze |├ (P) scroll_hold |├ (P) looping |├ (P) movement_block |├ (P) gravity |├ (P) match_content |├ (P) step_size |├ (M) scroll
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | bu5hm4n | T8096 efl.ui.collection | ||
| Resolved | None | T7870 efl.ui.grid | ||
| Resolved | None | T7881 efl.ui.list | ||
| Resolved | cedric | T7885 efl.ui.list_view | ||
| Resolved | None | T7891 efl.ui.scroller | ||
| Wontfix | bu5hm4n | T7882 efl.ui.scrollable_interactive | ||
| Resolved | None | T7883 efl.ui.scrollable | ||
| Resolved | None | T7921 enum Efl.Ui.Scroll_Block |
Comment Actions
scroll right now has a rect and a boolean flag for toggling the animation. With this you can say that the specified rectangle needs to be moved into the viewport. However, a user also might want to give a hint where the rectangle in the viewport wants to be (top-left ? center? top-right ?) A Position_2D with relative coordinates could be useful for that.
Comment Actions
I think a position would be way too descriptive; developers are just going to want to do top/middle/bottom.
@woohyun @Jaehyun_Cho can you tell us about app developer needs here?
Comment Actions
I think we need both things.
Position based scrolling is necessary in general case. and user can adjust target position and alignment by controling position and size value.
You can find an example in elm.genlist(_elm_genlist_item_coordinates_calc)
If we create new API that using Eo as paramter, hint of align is necessary.
For example efl_ui_scrollalbe_scroll_object(button, BOTTOM_CENTER);
Comment Actions
I think it will take more time to implement. so I will implement it in the next version.
Comment Actions
Okay, so we'll keep the current one as-is and add the other one at a later point? This is needed in the inheritance tree so it would have to be stable for this release...