On Sep 21, 10:19 am, Alex Holkner <[EMAIL PROTECTED]> wrote:
> 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 :-)
My editor is a simplified/bastardized version of the editor part of
Jef Raskin's The Human Environment, AKA Archy:
http://en.wikipedia.org/wiki/Archy
The nonstandard actions I need to support are
- overstrike: to get "composite" characters, you press more than one
key at the same time, instead of using dead keys.
- autorepeat: is only triggered if you press a key four or more times
consecutively (3 in the original Archy).
> > 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.
I'll do that, thanks.
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
-~----------~----~----~----~------~----~------~--~---
