AutoHotkey Community

[dvda2k]

A_EventInfo for WheelUp/WheelDown is lack of WHEEL_DELTA information, and doesn't work on many Microsoft mice.

I have a Microsoft mouse which has a hi-resolution wheel. Instead of sending 120 WHEEL_DELTA units (as a typical mouse does) per detent, it sends 28 units to the system.

USB Mouse has a 125Hz pooling rate. That means it tells the system what happened in every 8ms. If you turn your wheel really fast, say twice in 8ms, the mouse will combine these two wheel messages into one with an accumulated WHEEL_DELTA. For a regular mouse, it's 120 + 120 = 240.

The current A_EventInfo is a modulo of 120. If WHEEL_DELTA is 120 units, A_EventInfo = 1; If it's 240, A_EventInfo = 2, and so on.

The problem with my hi-resolution wheel is, unless you turn it every fast, A_EventInfo is always 0. Because Mod (28, 120) = 0 .Therefore you can't tell how many detents you really turned.

So please make A_EventInfo more detailed. I suggest simply taking the value of WHEEL_DELTA.

[BoffinbraiN]

Good suggestion. Normal wheels which 'tick' on each notch are good, but having wheels with higher DPI make the potential for accurate AND fast scrolling in applications even better.

I'm a bit of a scrollwheel freak too, as you can read here. :)

[dvda2k]

BoffinbraiN, thanks for your reply and your wheel script is interesting and has some really good documentation.

I wrote a wheel acceleration script in a different approach of yours. This post is probably not the best place to discuss it. I can reply to your post or whatever ways you like.

[BoffinbraiN]

Sure! That would be great.

[dvda2k]

I reconsidered my suggestion as taking WHEEL_DELTA value as A_EventInfo. It will cause backward compatible issue.

My new proposal is to introduce a "SetEventInfoMode, 1|2" directive. The default is mode 1, in most case A_EventInfo = 1, which is the current implementation. Mode 2 will use the WHEEL_DELTA value, in most case A_EventInfo = 120.