On 8/27/08, Danny Kutner <[EMAIL PROTECTED]> wrote: > > When at least two methods are scheduled at intervals and either the > window is minimized or restored or the frame rate limit is changed, > the interval of one or more changes. > > eg: > import pyglet > > def scheduledMethod1(dt): > print "scheduledMethod1", dt > > def scheduledMethod2(dt): > print "scheduledMethod2", dt > > win = pyglet.window.Window() > pyglet.clock.schedule_interval(scheduledMethod1, 0.5) > pyglet.clock.schedule_interval(scheduledMethod2, 0.5) > pyglet.app.run() > > > produces the result: > > scheduledMethod1 0.5 > scheduledMethod2 0.5 > scheduledMethod1 0.5 > scheduledMethod2 0.5 > scheduledMethod1 0.5 > scheduledMethod2 0.5 > scheduledMethod1 0.5 ##window minimized > scheduledMethod2 0.5 > scheduledMethod1 0.5 > scheduledMethod2 0.5 > scheduledMethod1 0.5 > scheduledMethod2 0.5 > scheduledMethod1 0.577999830246 ##window maximized > scheduledMethod2 0.577999830246 > scheduledMethod2 0.25 ##interval incorrect > scheduledMethod2 0.25 > scheduledMethod1 0.5 > scheduledMethod2 0.25 > scheduledMethod2 0.25 > scheduledMethod1 0.5 > scheduledMethod2 0.25 > scheduledMethod2 0.25 > scheduledMethod1 0.5 > > Any ideas?
Thanks for the bug report & test case. Fixed in r2228 (trunk) and r2229 (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 -~----------~----~----~----~------~----~------~--~---
