Final track in long Track listings hidden by horizontal scroll bar and cannot be seen for Mixx 2.2.3 (build 2.2 r6750) on MacOS Catalina with version 10.15.4

[Aaron Savage]

I looked and cannot see this bug being reported elsewhere so here it is. I am using a Mac Powerbook with MacOS Catalina 10.15.4 and using Mixx version 2.2.3 (build 2.2 r6750)

Processor : 2.2 GHz Quad-Core Intel Core i7
Memory : 16 GB 1600 MHz DDR3
Graphics : Intel Iris Pro 1536 MB

When viewing the track listings for any view source (Tracks, Auto DJ, Playlists, Crates, Computer, History, Recordings, Analyse & iTunes), the final track in a long list is always obscured by the horizontal scroll bar which is layered over the track. Obviously this only affects view sources where vertical scrolling is necessary, but every time vertical scrolling is necessary the horizontal scroll bar obscures the track information for the last track in the list.

Should be an easy interface fix with an allowance added below the final track for the scroll bar layer placement, but currently does interfere a lot with usability. I do not know if this affects other platforms, but if it does, fixing it will help a lot of users.

[Ian Edwards (denkyuu)]

Just wanted to add an extra bump for this bug. It's been on the tracker since 2018 (https://bugs.launchpad.net/mixxx/+bug/1800577) and it's pretty inconvenient.

Best two workarounds are still just to hide enough columns in the library until no horizontal scrolling is necessary or to go into MacOS General preferences and set scroll bars to always show.

MacBook Pro (Retina, 15-inch, Mid 2014)
2.8 GHz Quad-Core Intel Core i7
16 GB 1600 MHz DDR3
Catalina 10.15.6
Mixxx versions 2.3 AND 2.2.4

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/9994

[Daniel Schürmann (daschuer)]

I have prepared a test build linked at the GitHub issue https://github.com/mixxxdj/mixxx/issues/9495.
Please verify, if the issue is still reproducible with
Mixxx 2.3.5 or 2.4-beta and than check if the issue is fixed with the parched test build.
Thank you.