On Jan 3, 8:52 pm, Richard Jones <[EMAIL PROTECTED]> wrote:
> Ensure only one thread is doing actual pyglet stuff (rendering, event loop,
> etc). See how you go...

In particular, it's common for rendering systems to require all access
to be done from just one thread (sometimes only the main thread). For
a library to attempt to remove that restriction for you would probably
impose all sorts of locking overhead behind the scenes for very little
gain.

--
Ben Sizer

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pyglet-users" group.
To post to this group, send email to pyglet-users@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to