[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[pygame] Odd key code behaviour
- To: PyGame Users <pygame-users@seul.org>
- Subject: [pygame] Odd key code behaviour
- From: Magnus Lie Hetland <magnus@hetland.org>
- Date: Fri, 25 Jan 2002 19:51:32 +0100
- Delivered-To: archiver@seul.org
- Delivered-To: pygame-users-outgoing@seul.org
- Delivered-To: pygame-users@seul.org
- Delivery-Date: Fri, 25 Jan 2002 13:51:34 -0500
- Mail-Followup-To: PyGame Users <pygame-users@seul.org>
- Reply-To: pygame-users@seul.org
- Sender: owner-pygame-users@seul.org
- User-Agent: Mutt/1.2.5i
I just had a lot of trouble with K_UP... K_TAB worked just fine, but
not K_UP. Then I started to suspect that the trouble was that I was
using "event.key is K_UP" and not "event.key == K_UP". The latter is
safer, of course, but I assumed that K_UP had been used in generating
the event... After all, "event.key is K_TAB" worked just fine.
What is the difference between the two? Good/bad luck? :)
--
Magnus Lie Hetland The Anygui Project
http://hetland.org http://anygui.org
____________________________________
pygame mailing list
pygame-users@seul.org
http://pygame.seul.org