On 21/09/2007, at 10:36 AM, Esteban wrote:
> >> Is there a reason besides this issue you are using your own input >> method? >> i.e., is there some functionality here pyglet is missing? > > No, I'm missing nothing from pyglet in this area. I'm doing a text > editor with some idiosyncratic keypress/release->char semantics, so > it's normal that I need to work with key, rather than character, > events. I'm intrigued :-) > > One thing that I do miss for my application is the ability to block on > window events and timers. Contrary to (most) games, my app is fully > event driven and I'd rather sleep while there are no outstanding > events or timers (e.g., to save laptop battery while editing, and not > to hog CPU from other running programs), rather than polling all the > time. Yes, I would love this too, and is a high priority for future releases post-1.0. In the meantime use clock.set_fps_limit to at least avoid punishing the CPU. Cheers 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 -~----------~----~----~----~------~----~------~--~---
