![driver logitech setpoint driver logitech setpoint](https://logidownload.com/wp-content/uploads/2020/03/Logitech-Pilot-Wheel-Software-1.png)
(Applications that wish to behave differently can then re-route the message themselves.
![driver logitech setpoint driver logitech setpoint](http://wiki.robotz.com/images/f/ff/LogitechSetpoint03.png)
I first observed the Logitech WM_MOUSEHWHEEL problems some years ago (2009, SetPoint 4.80, Windows Vista 32-bit) and I believe they remain the same today (2012, SetPoint 6.32, Windows 7 64-bit). Anyway, today I'm here to rant about Logitech instead. Clearly, Microsoft are still stuggling to grasp the concept of these new-fangled hyperlinks and this whole 'world wide web' thing, but that is outside of my control. Despite their use of numeric components which render them arbitrary and meaningless to humans in the first place, links to Microsoft-run web servers are inevitably prone to breakage in the wake of the company's insatiable, inexplicable and inexcusable lust for moving content around without any kind of forwarding. I apologise in advance for when the various links to MSDN API documentation become broken.Logitech's mistakes only apply to the latter, horizontal case (WM_MOUSE**H**WHEEL) and their handling of the more common vertical case seems completely fine. Note 1 - WM_MOUSEWHEEL vs WM_MOUSEHWHEEL: I share my findings here to help other developers. The mistakes cause problems in many applications and I have personally wasted hours, if not days, battling them in my own code.
#Driver logitech setpoint drivers#
Logitech's SetPoint mouse drivers have serious mistakes in their handling of horizontal scroll-wheel messages ( WM_MOUSEHWHEEL).