Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ScrollArea adjustments for better configuration/customization #5406

Open
MStarha opened this issue Nov 25, 2024 · 2 comments · May be fixed by #5443
Open

ScrollArea adjustments for better configuration/customization #5406

MStarha opened this issue Nov 25, 2024 · 2 comments · May be fixed by #5443

Comments

@MStarha
Copy link
Contributor

MStarha commented Nov 25, 2024

I have a couple improvements in mind for ScrollArea that I would like to introduce. I am not sure whether these have been mentioned/worked on somewhere, I have not been able to find any besides #2163.

  • enable/disable scrolling by dragging the contained UI, dragging a scroll bar and mouse wheel scrolling independently of each other (currently, there's only ScrollArea::drag_to_scroll() and ScrollArea::enable_scrolling())
  • hide scroll bars when scrolling by dragging them is disabled
  • use Event::MouseWheel as input for mouse scrolling instead of reading PassState, as a result this will enable the user/programmer to consume the scoll event (though I am not sure whether implementing it this way will be possible, I have not tried yet - alternatively reading InputState could help)
  • scroll speed multiplier independent for each axis
  • support for custom cursor for hovering and dragging

I might add features that I come up with while working or take on other ideas and suggestions from here.

@juancampa
Copy link
Contributor

I just created this issue and was wondering if this is under your radar or something you'd like to include as part of these improvements:

Scroll is not locked to a nested ScrollArea

@MStarha
Copy link
Contributor Author

MStarha commented Dec 3, 2024

It does not fit inside the "configuration/customization" topic, so I think it is better to have a sepate PR for that. I might look into that once I am done with this issue, though I do not want to give you any false promises (I might not have time for that, unlike this issue which impacts me directly).

@MStarha MStarha linked a pull request Dec 6, 2024 that will close this issue
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants