On Jul 12, 10:00 pm, Richard Jones <[email protected]> wrote: > To disable the shadow context set the environment variable > "PYGLET_SHADOW_WINDOW=false"
Thanks. That takes care of the extra window, but keyboard events are still getting intercepted. (Ctrl+C doesn't even go through--I have to kill the process from somewhere else.) A clue is that *with* the shadow context, events would get to the console when I switched back and forth between the terminal app and the python shadow app. I've been reading over the pyglet.event documentation. I'm guessing that something important isn't happening that something like a Window would normally provide, but I don't quite understand how to fill the gap. Do I need to roll my own EventDispatcher to somehow pass along keyboard events? David --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
