You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I would like to control the drag_to_scroll behavior of the table contents. Currently, the scroll options assembled by the TableBuilder and passed to the ScrollArea do not include this option. That means the ScrollArea gets the default behavior, which is drag_to_scroll = true, but I may not want that behavior.
Describe the solution you'd like
I would add the drag_to_scroll flag to the table builder and allow the builder to populate this flag.
Describe alternatives you've considered
The only work around at the moment is to disable the scrolling in the table itself, and put the table into a scroll area, where you can control the option. However, this is not the same, as the header of the table will scroll off the area.
Additional context
I can put this on PR assuming it's a reasonable feature to have.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I would like to control the
drag_to_scroll
behavior of the table contents. Currently, the scroll options assembled by theTableBuilder
and passed to theScrollArea
do not include this option. That means theScrollArea
gets the default behavior, which isdrag_to_scroll = true
, but I may not want that behavior.Describe the solution you'd like
I would add the
drag_to_scroll
flag to the table builder and allow the builder to populate this flag.Describe alternatives you've considered
The only work around at the moment is to disable the scrolling in the table itself, and put the table into a scroll area, where you can control the option. However, this is not the same, as the header of the table will scroll off the area.
Additional context
I can put this on PR assuming it's a reasonable feature to have.
The text was updated successfully, but these errors were encountered: