Closed GoogleCodeExporter closed 8 years ago
Original comment by Benjamin.Heasly
on 23 Sep 2010 at 5:46
As of r387, mexHID openAllMatchingDevices and openMatchingDevice take an
optional isExclusive argument.
When true, will try for exclusive device access with the OS X/IOKit
kIOHIDOptionsTypeSeizeDevice option. The default is not to try for exclusive
access. If a device is already seized, opening will fail with negative status.
Aside:
I found that I had been using the HID manager wrong. I never needed to "open"
the manager because I was opening individual devices instead. I also never
needed to schedule the manager with the run loop. Opening and scheduling the
manager is really just there to open and schedule matched devices, which I'm
not trying to do.
I don't need to schedule devices with the run loop because I'm not using
device-level asynchronous functions. Only queues need scheduling, so far.
But I may later need to schedule devices...
Original comment by Benjamin.Heasly
on 24 Sep 2010 at 8:26
Original issue reported on code.google.com by
Benjamin.Heasly
on 7 Sep 2010 at 7:06