I just upgraded SDL from 1.2.9 and noticed a few differences with handling keys
in my program.
I’m using the ‘^’ key (under the Escape key) to toggle a quake-like console,
with 1.2.9 this used to be the SDLK_BACKQUOTE, now with 1.2.10 I had to redefine
it to SDLK_BACKSLASH.
Another thing I noticed is that in order to type a ‘?’ key in my app, I now have
to use Left-Shift+’?’ to actually get the ‘?’ unicode in SDLKeyEvent.
Here’s what I get when pressing the keys:
? -> code=91, unicode=223
Shift+? -> code=91,unicode=63
What could I be doing wrong or is it just a regular SDL change? I’m using
WindowsXP and a german keyboard by the way.
This was a bug in the switch from DirectInput to WinDib. It has been
fixed in SVN (post-1.2.10) and should be included in any wrap-up release
as well as anything in the 1.3 tree from what I understand.
So your best bet right now is to test against SVN.
–William
Glitch wrote:> Hello!
I just upgraded SDL from 1.2.9 and noticed a few differences with handling keys
in my program.
I’m using the ‘^’ key (under the Escape key) to toggle a quake-like console,
with 1.2.9 this used to be the SDLK_BACKQUOTE, now with 1.2.10 I had to redefine
it to SDLK_BACKSLASH.
Another thing I noticed is that in order to type a ‘?’ key in my app, I now have
to use Left-Shift+’?’ to actually get the ‘?’ unicode in SDLKeyEvent.
Here’s what I get when pressing the keys:
? -> code=91, unicode=223
Shift+? -> code=91,unicode=63
What could I be doing wrong or is it just a regular SDL change? I’m using
WindowsXP and a german keyboard by the way.
I’m using the ‘^’ key (under the Escape key) to toggle a quake-like console,
with 1.2.9 this used to be the SDLK_BACKQUOTE, now with 1.2.10 I had to redefine
it to SDLK_BACKSLASH.