Author Topic: Improper implementation of PgUp/PgDn keys in MusicBee  (Read 1863 times)


  • Newbie
  • *
  • Posts: 6
QUICK EDIT: I'm realizing now that this maybe could have gone in the Bug Report section instead. I suppose it's up to the dev whether or not he categorizes this as something that's 'working as intended' or not. Whether or not that is the case, it's most definitely an anti-user UI 'quirk'.


So it seems in MusicBee, the PgUp/PgDn keys work according to the current selectionand they move your selection down the up/exact number of rows that make up the viewing area.

Now, this is only the proper works okay in cases where there is no 'whitespace' between rows. (e.g.

But in cases where the current view is arranged in any way other than exclusively track rows, the PgUp/PgDn key tries to land on the row exactly one screen down - but if there is no row at that spot it KEEPS GOING until it lands on a track whose row are at those coordinates of the current view. Here is an example:

In this gif the selection is starting out at 'Never Say Die' by CHVRCHES and when I press PgUp exactly one time, the selection actually moves up several 'pages' worth of albums because I have a few albums there with only one track.

Here is a gif of my scrolling from the same starting point up to where one PgUp took me:

As you can see it's WAY more than one 'viewing area' sized page which is how PgUp/PgDn is meant to work. One PgUp scrolls me up several pages. =/

So is there any way to make the PgUp/PgDn buttons work in a way less jarring manner? Because as it stands, I can't figure out any way to scroll through my library in a reasonable manner like I would do in any other app. You'll see I posted another thread asking if it was possible to even set up a hotkey to jump to the next grouping. At least that would let me scroll through my music without flying past tons of stuff.
Last Edit: June 05, 2018, 09:54:52 AM by -VismundCygnus-


  • Administrator
  • Hero Member
  • *****
  • Posts: 33867
I can see it would scroll up/down way too much in some circumstances due to the view you are using. Its fixed for the next v3.2 update
unzip and replace the existing musicbee files
Last Edit: June 05, 2018, 06:02:44 PM by Steven


  • Newbie
  • *
  • Posts: 6
Shit yeah dude, that's what I call service with a smile! Thanks man!