[sorry to reply so late] Thanks for the tip about the 'dt' argument, but that doesn't change the outcome of the test (as a restart is supposed to be done anyway for normal use).
Any insight as to why the app.run() loop does not work as advertised ? tia, Dirk On Sep 24, 10:24 pm, "Alex Holkner" <[EMAIL PROTECTED]> wrote: > On 9/25/08,dirkjot<[EMAIL PROTECTED]> wrote: > > > pyglet.clock.schedule_interval(self.drawcounter.logentry, 5) # should > > be 5 seconds, right? > > > I use time.clock() for this, which should on windows at least be very > > accurate. > > Here is some partial code for the logging bit > > class TimeCounter(object): > > [stuff deleted] > > def logentry(self, restart=True): > > Can't tell if this affects your results, but note that when this > logentry method is called by pyglet.clock, it is called with a 'dt' > argument, which is causing 'restart' to always be truthful, so your > timecounter is being reset every iteration. > > 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 -~----------~----~----~----~------~----~------~--~---
