If you are one of the people who have encountered issues with scheduling accuracy in pyglet, please take a couple of minutes to run this test case on your computer. Your feedback would be especially helpful if you are running Windows, which apparently had some serious issues for some people in the past (though not all).
To run the test case, check out the latest revision of pyglet from SVN (instructions at code.google.com/p/pyglet/source/checkout) and run python tests/app/EVENT_LOOP.py Note that this version of pyglet is not stable and so not suitable for development -- don't install it. The test case will take no longer than 30 seconds to run. If the test case fails, please try it again. This sort of timing test case is bound to fail from time to time, due to nondeterminism in the operating system. You may need to quit background processes such as games or messaging software if you get repeated failures. After trying the test case at least 5 times and getting _no_ successes, please copy the output of one of the runs and email me. If it passes at least once, there's no need to email me. Cheers Alex. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
