Event.key.keysym.scancode

SDL Development
1

I working at creating a SDL driver for the Bochs Pentium emulator and
using the event.key.keysym.scancode really makes things easier, since we
can use a hardware reported value to simulate hardware (quite
effective).

The issue at hand is that the scancodes are offset by a value of 8 on
some systems but not on other systems. The escape scancode on my box
here locally reads as 0x09 when it should really be 0x01, but on one of
my fellow developer box, it is the expected value of 0x01.

Anybody have details about that? both systems where using SDL under a
X11 driver under a *nix environment.

Thanks for any detail on that one,–
EKS - Dave Poirier (instinc at users.sf.net)
“may the hairs on his toes never fall out” http://uuu.sf.net/

2

I working at creating a SDL driver for the Bochs Pentium emulator and
using the event.key.keysym.scancode really makes things easier, since we
can use a hardware reported value to simulate hardware (quite
effective).

The issue at hand is that the scancodes are offset by a value of 8 on
some systems but not on other systems. The escape scancode on my box
here locally reads as 0x09 when it should really be 0x01, but on one of
my fellow developer box, it is the expected value of 0x01.

Anybody have details about that?

The hardware scancodes are guaranteed to be different in various environments.
Use them at your own risk. :slight_smile:

See ya,
-Sam Lantinga, Software Engineer, Blizzard Entertainment