Richard, while you're in a committing mood, can you commit Adam's patch for issue 612?
https://code.google.com/p/pyglet/issues/detail?id=612#c2 I tested it, and it works great for me. It's also a much more elegant (and functional) solution than my quick-n-dirty attempt. ~ Nathan On Wed, Oct 10, 2012 at 4:09 PM, Adam Bark <[email protected]> wrote: > On 10/10/12 05:42, Nathan wrote: > > Absolutely. I reviewed all open issues, and found no existing relevant > ones, so I added this as issue 612. > > https://code.google.com/p/pyglet/issues/detail?id=612 > > ~ Nathan > > On Tue, Oct 9, 2012 at 1:03 PM, Adam Bark <[email protected]> wrote: > >> It might be good to document it if you can be bothered. >> > Thanks. I've posted a couple of things including a work around that I > would like opinions on. > Cheers, > Adam. > > -- > 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. > -- 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.
