Hi there, Thanks for the input. On Sep 18, 11:31 am, Richard Jones <[email protected]> wrote: > On 18/09/2009, at 8:22 PM, Tartley wrote: > > > def draw(image): > > image.blit(0, 0) > > Have you checked that this gets called when the window is damaged? It > sounds like the window's getting damaged and the on_draw isn't being > invoked as a result... > > Richard
If I add "print '.'," to the draw function, then I see it geting called as I move the mouse around over the pyglet window. If I add a "clock.schedule(lambda _: None)", then I see the draw function getting called continuously. Although, to be honest, with hindsight I realise that I am confused about how my own code was working. How come setting the opengl projection/modelview matrices affected the image.blit()? Presumably it's not a real old-school "blit" as I understand the word, but is simulating one using a texture mapped quad? Or am I completely confused? I'm still suffering from the lingering effects of a nasty flu, and although I'm on my feet again, I'm finding that I'm distinctly poor at thinking clearly. I may well be doing something completely stupid. I'll investigate more in a few days when hopefully I have a clearer head, and will have fixed up my multi-monitor desktop at home, so I can experiment there. Thanks heaps for everyone's input to date. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
