On 8/19/08, Alex Holkner <[EMAIL PROTECTED]> wrote: > I've put in what I think is a good fix (a compromise between the two > goals, using a heuristic of 200ms for judging when the clock is > ticking "slowly"). I can't commit right now (some gateway error > between here and googlecode), but I'll try again in the morning (AEST) > and let you know when it's in trunk and pyglet-1.1-maintenance.
Fix is in r2201 (trunk) and r2202 (pyglet-1.1-maintenance). 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 -~----------~----~----~----~------~----~------~--~---
