Wow, that was fast--thanks for fixing it! Sorry about the name; at the time I made it, I was really baffled at how such a big bug could have evaded notice for so long in such a popular library, and so that's just the first name that came to mind. Yes, bugs are rampant everywhere, and no offense to Pyglet, which I have actually switched to from Pygame.
Do you know why the those functions got called when I put break points in them? It's like quantum mechanics--it only works properly if I look at it, and only breaks if I don't. Here's another analogy: The mail man is supposed to come every week day, but there is a bug: he never comes on Fridays. So, I research where he lives and set up a camera by his bedroom window, which I look at on random Fridays. Every Friday that I check the camera, he gets out of bed and delivers the mail, but every Friday that I don't check the camera, the mail doesn't come. Perhaps he notices the camera? In the case of the code, I suppose that breakpoint modifies how the function is treated, somehow. Ah, I see you provided a link. I'll go check it out now, thanks again for the quick action! -- 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 pyglet-users+unsubscr...@googlegroups.com. To post to this group, send email to pyglet-users@googlegroups.com. Visit this group at http://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
