On 12/31/08, __doc__ <[email protected]> wrote: > So I don't see any usable path to get: > 1) raw mouse input
This depends on your hardware. From pyglet's point of view, if you have an HID mouse that is exposed via the Linux evdev API, it will expose its events. Otherwise, you're out of luck (short of writing your own kernel driver). > 2) joystick input evdev was chosen on Linux because joydev doesn't have anywhere near the capabilities needed to match features with Windows and OS X -- it just wouldn't fit into the pyglet joystick API (which, for example, allows for joystick enumeration and inspection). You'll need to add a local udev rule to give users permission to use your joystick device via evdev. While this isn't ideal, I don't think it's unreasonable. Alex. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
