Ensure amount of scroll wheel rotations always captured accurately regardless of settings that affect size of scroll delta

[Inwerpsel]

Currently, a fixed step size of 100 is used to calculate the amount of steps (individual rotations of a stepped mouse scroll wheel) to capture during wheel events. This is used for scrolling over the history component and scrolling over the frame scale slider.

It produces an accurate result even when the event fires with a longer delta. This happens if the wheel is scrolled fast enough and/or a long running task delays the event.

This is probably the default step size on most devices, but I'm sure it can have another value depending on multiple factors in the environment.

Since the amount of steps is rounded to the nearest integer, step sizes between 50 and 100 should still have the same behavior when scrolling one at a time, and only when the delta comprises multiple steps would become somewhat slower.

Values below 50, however, will result in 0 steps because of rounding down.

Deltas above 150 would make it impossible to scroll one at a time.

Todo

• Figure out common possible values for the delta and which factors affect its size
• Test what happens when using continuous scrolling (unlocked scroll wheel)
• Test what happens on alternative "scrolling" techniques (swiping on touch screens, custom scroll controls on a keyboard)
• If necessary, add configuration for the step size. Could request user to scroll mouse a single time and capture