#Logitech setpoint drivers#
#Logitech setpoint driver#
#Logitech setpoint code#
#Logitech setpoint windows 7#

Instead of - or rather, in addition to - those rules, Logitech do the following:.If WM_HSCROLL is sent to a window then it is explicitly for that window and no other.) (Note: WM_HSCROLL messages are not propagated the way mouse-wheeel messages are.

#Logitech setpoint driver#

If no window swallows the message, DefWindowProc will run out of parent windows and might then decide to turn the message into WM_HSCROLL or whatever, but that is up to DefWindowProc and the Win32 API itself, not something the mouse driver should be involved with.I believe that DefWindowProc will always return zero for the message, but I have not checked and it should not matter.) It only matters whether or not DefWindowProc is called. (At least in this respect, it does not actually matter what the WM_MOUSEHWHEEL return value is.By not calling DefWindowProc, the window 'swallows' the message that is, it ensures it is not propagated to or processed by any further windows. scroll something) and then return without calling DefWindowProc. A window which handles WM_MOUSEHWHEEL should do whatever it needs to do (e.g.DefWindowProc will, in turn, send the message to the parent window, where the process repeats. A window which does not handle WM_MOUSEHWHEEL should (as with any unhandled message) pass it toĭefWindowProc.Let me describe the standard Win32 behaviour in more detail:.There should be no internal forwarding of the message, since DefWindowProc propagates it up the parent chain until it finds a window that processes it. MSDN clearly states: The DefWindowProc function propagates the message to the window's parent.Logitech wrongly convert WM_MOUSEHWHEEL into WM_HSCROLL if you return zero:.

#Logitech setpoint drivers#

Applications that handle WM_MOUSEHWHEEL need to return non-zero to tell Logitech's drivers that they have handled the message. While Logitech get it right with vertical messages, they do the opposite with horitontal messages.MSDN clearly states: If an application processes this message, it should return zero.Logitech wrongly interpret the WM_MOUSEHWHEEL return value:.This can be particularly troublesome when the message is sent to controls which can never gain the input focus and thus do not anticipate receiving scroll-wheel messages.They do this even if the application does not have the focus.

They do this even if the control does not have the focus.

While Logitech do the right thing with vertical wheel messages, they send horizontal wheel messages to whichever control is under the mouse.

It is not the job of the mouse driver to do that re-routing.) (Applications that wish to behave differently can then re-route the message themselves.

Scroll-wheel messages are supposed to go to the control with the input focus.

Logitech send WM_MOUSEHWHEEL to the wrong window:.

The WM_MOUSEHWHEEL problems are as follows:

#Logitech setpoint code#

It is possible that some of the finer details have changed, but the main observations and workarounds should still be good and remain in use by code that I maintain and use every day with my Logitech mouse.

#Logitech setpoint windows 7#

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. Logitech's SetPoint mouse drivers have serious mistakes in their handling of horizontal scroll-wheel messages ( WM_MOUSEHWHEEL).