[GH-ISSUE #42] Scrolling doesn't work in menu screen until carousel is touched #23

New issue

Closed

opened 2026-02-28 15:41:46 +03:00 by kerem · 2 comments

kerem commented

2026-02-28 15:41:46 +03:00

Owner

Originally created by @b16tran on GitHub (Nov 24, 2024).
Original GitHub issue: https://github.com/usenocturne/nocturne-ui/issues/42

Originally assigned to: @brandonsaldan on GitHub.

Carousel selection isn't active until you interact with it by touching. Aka if I select Library, I expect to be able to start scrolling. I should always be able to scroll on the current tab selected.

Or by default the scroll knob should switch between the tabs on the left and when knob button pressed, goes into the carousel on the right from which you can scroll. Then if you click back, it goes back to the tabs for scrolling. There already is the little line on the left indicating the active tab, that can be extended to move over to above the album art when you enter the carousel context.

Originally created by @b16tran on GitHub (Nov 24, 2024). Original GitHub issue: https://github.com/usenocturne/nocturne-ui/issues/42 Originally assigned to: @brandonsaldan on GitHub. Carousel selection isn't active until you interact with it by touching. Aka if I select Library, I expect to be able to start scrolling. I should always be able to scroll on the current tab selected. Or by default the scroll knob should switch between the tabs on the left and when knob button pressed, goes into the carousel on the right from which you can scroll. Then if you click back, it goes back to the tabs for scrolling. There already is the little line on the left indicating the active tab, that can be extended to move over to above the album art when you enter the carousel context.

kerem closed this issue

2026-02-28 15:41:47 +03:00

kerem commented

2026-02-28 15:41:47 +03:00

Author

Owner

@BBaoVanC commented on GitHub (Nov 24, 2024):

I think what's happening is that the cursor is at the position where you last tapped. Then, if the component that should be scrolled by the dial doesn't happen to be under that spot, scrolling doesn't work. Perhaps nocturne-ui should override scroll wheel events and redirect them to whichever should be the main, scrollable component on the current page.

@BBaoVanC commented on GitHub (Nov 24, 2024): I think what's happening is that the cursor is at the position where you last tapped. Then, if the component that should be scrolled by the dial doesn't happen to be under that spot, scrolling doesn't work. Perhaps nocturne-ui should override scroll wheel events and redirect them to whichever should be the main, scrollable component on the current page.

kerem commented

2026-02-28 15:41:47 +03:00

Author

Owner

@kenhayward commented on GitHub (Nov 26, 2024):

Further to this, if you click back to get to recents from now playiong the scroll wheel works immediately, if you then click on library the scroll wheel no longer functions until you touch the screen - supporting the previous commenters point

@kenhayward commented on GitHub (Nov 26, 2024): Further to this, if you click back to get to recents from now playiong the scroll wheel works immediately, if you then click on library the scroll wheel no longer functions until you touch the screen - supporting the previous commenters point

No labels

help wanted

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nocturne-ui#23

No description provided.

Rows
Columns