- 15 May, 2014 38 commits
-
-
Piotr Caban authored
-
Piotr Caban authored
-
Stefan Dösinger authored
-
Stefan Dösinger authored
-
Nikolay Sivov authored
-
Nikolay Sivov authored
-
Nikolay Sivov authored
-
Nikolay Sivov authored
-
Jacek Caban authored
-
Martin Storsjo authored
-
Martin Storsjo authored
-
Jacek Caban authored
-
Huw Davies authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Hans Leidekker authored
-
Hans Leidekker authored
-
Hans Leidekker authored
-
Hans Leidekker authored
-
Hans Leidekker authored
-
Hans Leidekker authored
-
Frédéric Delanoy authored
-
Huw Davies authored
-
Huw Davies authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Nikolay Sivov authored
-
Ken Thomases authored
The Mac driver can generate scroll wheel events with values which are not integral multiples of WHEEL_DELTA. Apps should handle that by scrolling a corresponding non-integral multiple of what they'd do for a WHEEL_DELTA-valued scroll or, if they can't, then at least accumulate scroll distance until its magnitude exceeds WHEEL_DELTA and do a "chunky" scroll. However, many apps don't do that properly. They may scroll way too far/fast or even in the opposite direction. If the registry setting UsePreciseScrolling is set to "n", the Mac driver will do that accumulation and chunking itself to work around such broken app behavior.
-
Ken Thomases authored
-
- 14 May, 2014 2 commits
-
-
Shuai Meng authored
-
Jacek Caban authored
-