Aha, this has fixed it! Being a tiny test project, I hadn't even considered the event queue filling up!
Thank-you very much indeed! On 21 July 2013 21:12, DR0ID <dr...@bluewin.ch> wrote: > Am 21.07.2013 17:41, schrieb Andrew Barlow: > > This is just some testing code that demonstrates it. > > > https://docs.google.com/file/d/0B40CJaTKX9a_UjN2V2RJc3Z0NmM/edit?usp=sharing > > Testing on Windows at the moment. > > The little unit should shuffle left and right whilst the app is running. > This works fine until you move the Window. > > > On 21 July 2013 16:32, Noel Garwick <noel.garw...@gmail.com> wrote: > >> Please upload the code so others can test. >> On Jul 21, 2013 11:18 AM, "Andrew Barlow" <andrew.bar...@gmail.com> >> wrote: >> >>> Hello! >>> >>> I'm currently just playing around with the PyGame sprite prefabs and I >>> was wondering if anyone had ever come across the issue where if you move a >>> windowed PyGame that's using LayeredDirty, all updates stop rendering? >>> >>> It looks like the game loop is still running, but my screen drawing >>> seems to stop (even though the list of dirty rects keeps populating). The >>> Window title even says "Not Responding" but the Python console output >>> continues to print my dirty rects. >>> >>> Any ideas as to why this might be? >>> >>> I think its got something to do with the switching between updated >>> regions and fullscreen updates in the LayrerdDirty group, but I really >>> don't know! >>> >>> I can upload a zip of the code if that's of any help? >>> >>> Any help with this would be hugely appreciated! >>> >>> Cheers >>> >> > > Hi > > You need to pump the event queue somewhere in your main loop! > > Either > > pygame.event.pump() > > or one of the event methods > > pygame.event.get() > pygame.event.wait() > > Otherwise the windows gets unresponsive after some time or some number of > events that fills up the event queue (mouse generates many events). > > If you still have the bug, write again. > > ~DR0ID >
