| 
      
      
      From: Bob S. <m24...@ho...> - 2006-06-16 05:23:32
      
     | 
| I'm trying to use libusb to retrieve mouse input, and I've noticed that when using a loop containing usb_interrupt_read in the form of a separate thread, WM_TIMER, or brute force iterations, that the loop runs at 40Hz (40 mouse inputs per second). The only exception is when I use the asynchronous read API calls and use about 8 contexts, then getting a rate of about 90-110 inputs per second. I noticed by using that hack of a method that the OS cursor was getting erratic, which suggests the OS is still fighting over the inputs for the device. The questions I have are... 1. What's causing this 40Hz frequency instead of the expected 125Hz? 2. Is it possible to get libusb-win32 to have exclusive access over the device? |