Hi LenardI figured out that you were deliberately vague, but I thought that he might use some more specific help based on his response ("Well, it was not doing anything anyway, so I commented it out. The error is now gone"). This looked for me as he didn't find the real problem (which is the combination of lines 38, 40 and 68, as you state in the latest emails).
For the ctrl-arrow problem: on win systems the ctrl-arrow causes the cursor to move from word to word in a text editor (instead from character to charachter). This is probably a special event send on the windows message queue which pygame does not handle as far as I know.
~DR0ID On 22.05.2010 00:26, Lenard Lindstrom wrote:
Hi DROID,I was being deliberately vague because I understand Alex is a student, and this is a project (?). As for the crtl-down, that doesn't appear to be Pygame. It doesn't cause a window switch on me for instance. So it is being handled before it reaches Pygame. Could it be an Accessibility feature?Lenard DR0ID wrote:On 21.05.2010 22:14, Alex Hall wrote:Well, it was not doing anything anyway, so I commented it out. The error is now gone, but my ctrl-down is still acting very strangely, acting like I had hit alt-tab or another keystroke to switch focus out of the pygame window and into the window behind it.HiTake a look at line 38, there you quit pygame, but in line 68 (which you took out) you tell the loop to continue. If you quit pygame and still call pygame.event.get() you get the video not initialized error (took me a while to see what Lenard said).For the odd behavior of you ctrl-down, I'm not sure what should happen, so I cant tell if it is doing what you want it to do.~DR0ID