Pyglet 1.2 alpha DEFINITELY broke the scheduling. I see people asking the
same thing, why the clock.set_fps_limit which previously worked is now no
longer working as advertised, and the response seems to be Oh, just don't
use it, and schedule everything on time intervals. Which is fine unless you
WANT sometime to fire each frame.
I'd appreciate some explanation of why this happened.
And a question to pyglet users who may have solved this problem before: If
i want to synchronize an animated sprite, such that it switches images on
each frame, how would you accomplish this? From testing this myself,
scheduling the image swaps to happen 1.0 / FPS_LIMIT isn't sufficient to
guarantee that it is synchronized; sinec clock.schedule doesn't work as
advertised, how else are you supposed to be able to do this?
On Saturday, 22 December 2012 00:40:25 UTC-5, Ricky Christie wrote:
>
> So I was trying out pyglet1.2alpha in my Snow Leopard.
> Either the pyglet.clock.tick() method doesn't get called periodically or
> the draw method doesn't.
> I wrote a code that should display incrementing number on each draw. It
> does increment but only after a long while.
>
> import pyglet
>
> class TestTick(object):
> def start(self):
> self.x = 1
> window = pyglet.window.Window()
>
> @window.event
> def on_draw():
> window.clear()
> self.x += 1
> label = pyglet.text.Label('Hello, world ' + str(self.x))
> label.draw()
> print('draw called')
>
> pyglet.app.run()
>
> test = TestTick()
> test.start()
>
> Am I using it wrong here?
>
--
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pyglet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
