PyGame and Windows 7 woes

Falun on 2010/08/07 05:08

Has anybody else had problems with pygame freezing up when running in Win7?

Typically my code will be fine... until I move the window and then it completely locks up and becomes unresponsive. Sometimes it's like that out of the gate and ever so occasionally it will work.

Just wondering if anyone else has seen behavior like this?

(log in to comment)

Comments

ServalKatze on 2010/08/07 08:49:

I have Win7 and haven't encountered any pygame-related problems yet. Which version of Python+Pygame do you use? Do you have problems with other pygame programs, too?

Falun on 2010/08/08 02:59:

I'm running python 2.6.5 and pygame 1.9.1

Falun on 2010/08/08 02:59:

...and I haven't tested too much with other pygame stuff since this started happening. I should do that.

Falun on 2010/08/08 06:15:

So my teammate Blake figured this one out... it had to do with my framerate limiting code -- "when you move the window, the eventing stops for a second causing your delay to be significant and making the difference negative" I was then trying to time.sleep(delay-less-than-zero) which got converted into a "wicked ass big positive number," to quote brave leader

saluk on 2010/08/08 07:22:

Ha, nice. I *love* how moving windows around in something called WINDOWS makes the application freeze.

adrwen on 2010/08/08 11:55:

Well, it's Microsoft's new approach to preventing piracy, they figured if people are so keen moving windows around on their own computer, they would soon start moving Windows between computers. :)

ikanreed on 2010/08/09 00:28:

I'd hate to say it, but that's python's fault. time.sleep should should raise an exception on a negative number. Windows is acting as designed, as a window that is being moved may misinterpret messages if
they were passed during the move, since window movement is asynchronous.