Doesn't it make more sense - given two incompatible event loops - one gui based and one network based - to give the network loop priority, and have it call back into the gui loop? Very generally speaking a gui tends to demand less responsiveness than the network (though this may not be the case on current hardware for the kind of applications that people are targeting with pyglet).
Can pyglet app EventLoop develop a non-blocking step()/pump() or some such name alternative to run()? John --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
