endless WM_MOUSEWHEEL events
-
I'm trying to handle mouse wheel events in the WndProc function and wrote c++ code that works fine with one mouse that has a fly-wheel. I tried the same code with another mouse and I get endless WM_MOUSEWHEEL events when I move the mouse wheel just one notch. Anyone know why this is happening?
-
I'm trying to handle mouse wheel events in the WndProc function and wrote c++ code that works fine with one mouse that has a fly-wheel. I tried the same code with another mouse and I get endless WM_MOUSEWHEEL events when I move the mouse wheel just one notch. Anyone know why this is happening?
-
Sounds like a possible hardware error. Does it happen in other applications with the "bad mouse"?
One of these days I'm going to think of a really clever signature.
-
It seems very odd that one mouse works correctly but the other generates lots of messages. That implies that there is something wrong with the second mouse.
One of these days I'm going to think of a really clever signature.
-
no, it works fine. It is definately not hardware. I could be that one mouse is fly wheel and other is not, or it could be that the code I'm using is wrong in someway
-
Could it be a "helpful hidden feature" of the mouse-driver? :)
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] They hate us for our freedom![^]
-
No, it would not; some programmers would simply take the first message, and ignore the repeating drivel, just like you would with spurious wm_mousemove messages. Update the drivers :)
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] They hate us for our freedom![^]
-
No, it would not; some programmers would simply take the first message, and ignore the repeating drivel, just like you would with spurious wm_mousemove messages. Update the drivers :)
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] They hate us for our freedom![^]
-
Not really. There's no way to tell which are real events and which are the spurious ones. At least, there's no way I know.
You haven't posted any code or shown what any of the "extra" WM_MOUSEWHEEL events you are getting look like and unfortunately, my crystal ball is in the shop, so you might want to post that kind of information. My guess is that its something in your code, but until I see the messages or your code, I can't really give you any advice beyond that. Darn crystal ball shop, they are taking FOREVER to get my ball fixed.