Hmm. Searching the other posts, I found this.
Essentially, I think it means that if you start from a listener event call and have an infinite loop where you don't return, only then do you tie up the EventQueue and no more events can be called until the method with the loop returns.
Does the GameWindow constructor start the game loop? If so you might be blocking the AWT event thread. Try constructing your GameWindow in a different thread.
1 2 3 4 5 6
| Thread t = new Thread() { public void run() { new GameWindow(); } }; t.start(); |
Kev
This would explain why I thought that a loop would tie up the events, just for the wrong reasons.
Sorry if this isn't right either. (me a n00b)