On Fri, Jan 23, 2009 at 9:43 AM, __doc__ <[email protected]> wrote: > > On Jan 22, 9:19 pm, Alex Holkner <[email protected]> wrote: >> The Joystick class normalises axis values, > The evdev wrapper passes the values trough unnormalized on r2428
Are you checking the Joystick.[xyz] values, or the underlying axes that the joystick is using? > >> and the Tablet class throws them away and uses window coordinates instead. > I haven't toyed with my tablet yet, but I can imagine situations where > it would be desirable that the input is mapped to a sub-region of the > window. Possibly, but not really feasible. Tablet drivers make a mess of the coordinate systems, and alternately give device coordinates (with no calibration data), window coordinates, screen coordinates, or something else again. As with joysticks, if you are willing to implement a calibration phase, you can access the raw device values and treat them any way you like, but pyglet does not attempt to interpret them this way. 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 -~----------~----~----~----~------~----~------~--~---
