On Dec 13, 3:21 am, Jonathan Peirce <[email protected]> wrote: > Hi there, > > I've just been playing with the joystick support in the pyglet repository. > I had to make a few minor tweaks on OSX (10.6 using framework python > 2.6.6 32bit) so that it used the cocoa (darwin_hid) instead of trying to > use carbon.
Alex's code in carbon_hid is used by default if you're running the carbon-based pyglet code. I rewrote the code in darwin_hid so that it would be 64-bit friendly. You can set pyglet_options['darwin_cocoa'] = True or run in 64-bit python to use the darwin_hid code (although this also forces you to use the cocoa-based windowing). I suppose that there's no reason why you couldn't use darwin_hid with the carbon pyglet, but it does require OSX 10.5 or later. > But then I ran into the slightly weird issue that all the axes are > initiliased as having value=None and this doesn't change for each axis > until the first detected movement on that axis. I guess this is because > of the event-driven design. Is it possible to trigger a series of fake > events during device.open() so that it fetches the true current values > on the axes? I'll see if I can look into it, although I may not have a joystick that demonstrates the problem. --phillip -- 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.
