Lenard Lindstrom ha scritto:
James Paige wrote:
On Tue, Sep 04, 2007 at 05:09:14PM +0200, pistacchio wrote:
Greg Ewing ha scritto:
pistacchio wrote:
while not done:
pygame.display.flip()
for event in pygame.event.get():
if event.type == QUIT:
done = True
Note that pygame.event.get() doesn't block, so you're
spinning in an extremely busy loop here. The screen
mightn't be getting a chance to update.
Try putting a pygame.event.wait() call in the loop.
--
Greg
hi there! still nothing.. i've altro tried with pygame's event pump
and wait and stuff, and nothing. then, the program worked
beautifully without a problem.. till a reboot of the computer, when
the same code (now) shows the same problem..
Are you using the IDLE editor? I seem to remember some talk about it
causing problems similer to this. There was a command-line option
that you had to add to make it run programs in a separate
interpreter, which prevented its own event handler from colliding
with pygame's
---
James Paige
The IDLE problem isn't really a problem as such. Being an interactive
session, the interpreter doesn't shut down when the Pygame code
finishes. So pygame.quit is not called and the window remains visible.
Restarting the interpreter or adding an explicit pygame.quit() closes
the window. As for the OPs example code, I put it in a file and
double-clicked. Worked fine.
oh, thanks, this helped a lot. would the situation change with a
different ide? any suggestion? (again, i'm working under windows xp)
this thing that i have to work around the problem every time that the
program rises an error or an exception it is quite boring as, like you
made me understand, the cycle doesn't come to the point where it quits
all the processes and hence pygame and i have to wait, termnate it and,
in a word, lose 30 seconds every time i want to change a comma in the code.
thanks.
