My understanding is that the scancodes -should- be in the same physical
location on every keyboard, whereas the keycodes will vary between keyboard
layouts. I think the SDL wiki sums up the situation pretty well:
I read an SDL mailing list post about this recently, and the reason for the
current implementation (if I remember correctly) was:
Sometimes you want the locations to be the same, such as WASD should be
handled the same, regardless of what the keys are called. In other
instances, such as pressing "I" to bring up "Inventory", you want the key
to represent the actual letter of the alphabet.
On Tuesday, October 11, 2016 at 2:25:17 PM UTC+9, swiftcoder wrote:
> I'm had thought that SDL keycodes are stable across keyboards and keyboard
> At any rate, Apple's scan codes are definitely stable across
> On Mon, Oct 10, 2016 at 6:04 PM, Benjamin Moran <benmo...@gmail.com
>> I've read about this issue a bit, and think that it would be nice to have
>> both available. Maybe it would be nice if the input events returned both.
>> You received this message because you are subscribed to the Google Groups
>> "pyglet-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> To post to this group, send email to pyglet...@googlegroups.com
>> Visit this group at https://groups.google.com/group/pyglet-users.
>> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
Visit this group at https://groups.google.com/group/pyglet-users.
For more options, visit https://groups.google.com/d/optout.