That is, how to translate those smaller ticks to smaller scroll increments (possibly sub-line scrolling) or accumulating them for a while until some threshold is reached at which point it scrolls a line or whatever unit feels appropriate for the application. Those messages deliver to the application a count of "ticks smaller than a notch" and the applications have to decide how to handle them.
To support smooth scroll, and even more accelerated scroll depending on the way you "rotate" the wheel, and match more or less properly what happens when you move fingers through a trackpad, slowly or quickly, the application has to handle additional Windows API messages. You know those mouse wheels which had notches which you could feel when rotating the wheel. So it lives in the late '90s when scroll was a matter of knowing "by how many lines should I scroll the content when I get 1 notch from the mouse wheel". The code editor of Visual Studio (2019) does not do so. In order to implement proper reaction to "smooth scrolling", as modern mice can support it or trackpads, the application best needs to handle some specific messages in the proper way. There are multiple ways to support scrolling inside an application, from a developer point of view.
0 kommentar(er)
