Re: [Libusb-win32-devel] 40Hz mouse polling rate?

[Bob S. <m24...@ho...>]

That method is still going to be problematic.

The idea I had for libusb-win32 was to use it as an alternative input method 
for a Quake engine port.

The reason is that GDI input, Windows XP rawinput, and DirectInput have a 
few issues:
- Windows XP rawinput only works with Windows XP, and 2000 is a target 
platform.
- DirectInput will enumerate more than 1 mouse only under Windows 98SE or 
ME.
- GDI input can't register separate mouse inputs.
- Some gaming mice report extra information not properly handled.
- Different model mice only report certain buttons to different API. (As in 
some only report all buttons to DirectInput, some only report to GDI, some 
only to rawinput)

Thus libusb-win32 looked like a possible alternative. Unfortunately, 
considering the drop-in nature of the engine itself, the user base probably 
wouldn't be too comfortable with installing specific device drivers.