> 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. 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. Then again, that isn't a high priority for me. I haven't yet checked whether this is a significant performance issue, and if it ever proves one and this hasn't been solved by then, I'll roll my own and contribute it. I thought I'd just check anyway, just in case there is anything I'm missing or in the plans. Thanks for the great work in pyglet! Esteban. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
