Good catch, finally I can replicate it!

To be fixed as https://www.ventismedia.com/mantis/view.php?id=16342

OK, so there is also this related observation regarding an associated mouse setting, as reported above

I also noticed that MM5 is inconsistent with regard to Windows mouse settings (Windows_key Mouse). ... eg. The setting is ignored in the Media Tree ... And ignored in EntireLibary|AllTracks ... but is obeyed within a global filter (ie. the magnifying glass on the right hand side)?

Hi,
1) The Option [Info Paneel] is not displayed
2) The error also occurs if you only work in one tab
3) The scroll speed is correct when scrolling using keyboard

The error occurs on the following nodes:
Playlists
Entire Library: Location
Folders: Location
Search results

All other nodes works correctly, for example: Entire Library: Genres / Artists / Rating

The error occurs on the following Windows Setting:
Mouse - Roll the Mouse wheel to scoll: One Screen at a time

The scroll speed works correctly by the following setting:
Mouse - Roll the Mouse wheel to scoll: Multiple lines at a time

I think the problem is the mouse-setting: Roll the Mouse wheel to scoll: One Screen at a time
It has no effect - one screen is not scrolled (this setting has the same effect as: Multiple lines at a time).
Or slow scroll speed (Nodes Entire Library: Location / Folders: Location / Search results / Context: Find more from Same ...)

Best Regards from Germany / Viele Grüße aus Deutschland

Hi, unfortunatelly we still cannot replicate even when using the same (black) skin and even when using artist with thousands of tracks in the list view.

Could you please try whether it happens also when
1) 'Info panel' sub-view is enabled in the view: https://www.dropbox.com/s/i2kyvgqv1xpwx ... 2.png?dl=0
2) Whether the tab used has an impact on it? i.e. does the same happen when scrolling the "Van morrison" artist list in the first tab?
3) is it related only to mouse wheel or does it happen also when scrolling using keyboard (up/down arrows or PgUp/PgDown) ?

here is a video from the error

in both tabs i use same scroll speed

https://youtu.be/gn_fIvp6YRg

we run Win10 Desktop with NO Touchscreen.

hhoff wrote: ↑Tue Feb 04, 2020 12:18 am A mouse wheel rotation in the player window (Playing) moves the content up or down by 5 lines.
In a search window does not move the content line by line, but only in very small sections.

OK, I don't see that.

"search window" = one of these? ... or something else?

View|Mode set to Desktop or Touch? ... I am in Desktop.

Anything else in your environment, that you can think of, which may explain the difference that we are seeing?,

A mouse wheel rotation in the player window (Playing) moves the content up or down by 5 lines.
In a search window does not move the content line by line, but only in very small sections.

hhoff wrote: ↑Mon Feb 03, 2020 11:06 pm Normally, turning a mouse wheel moves 5 entries down (or up). Are entries listed via search or 'find More from Same', mouse wheel movements tuning the list down in very very small steps.

I tried to reproduce what you are seeing, but don't see exactly what you describe . I tested global search, and contextual search, and also Find More Of Same.

I see that they are taking just 4 steps, instead of 5 ... is that what you are seeing?

I also noticed that MM5 is inconsistent with regard to Windows mouse settings (Windows_key Mouse). ... eg. The setting is ignored in the Media Tree ... And ignored in EntireLibary|AllTracks ... but is obeyed within a global filter (ie. the magnifying glass on the right hand side)?

They also ignore horizontal scroll wheels, on mice that have them.

Normally, turning a mouse wheel moves 5 entries down (or up). Are entries listed via search or 'find More from Same', mouse wheel movements tuning the list down in very very small steps.
I'm from Germany and hope the translation is understandable...

Hi,
Not sure I understand. Can you please explain the steps in bit more details?

MediaMonkey 5.0.0.2226 Beta

The mouse wheel does not work correctly for search results. This was also the case in older versions.