We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 597

Summary: windib + AltGr broken
Product: SDL Reporter: Alistair John Strachan <alistair>
Component: eventsAssignee: Sam Lantinga <slouken>
Status: RESOLVED WORKSFORME QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2 Keywords: target-1.2.14
Version: HG 1.2   
Hardware: Other   
OS: Windows (All)   

Description Alistair John Strachan 2008-06-19 04:44:17 UTC 
On a UK keyboard layout, the AltGr key is mapped to SDLK_RALT in X11.

On Windows, AltGr does not behave like Alt in most applications, but with SDL the SDLK_RALT sym is also generated (not SDLK_MODE as is erroneously documented).

With SDL_VIDEODRIVER=directx, SDLK_RALT is sent for this key on both SDL_KEYDOWN and SDL_KEYUP. However with SDL_VIDEODRIVER=windib (recently the default), SDLK_LCTRL (incorrect) is sent for SDL_KEYDOWN and SDLK_RALT (correct) is sent for SDLK_KEYUP.
Comment 1 Alistair John Strachan 2008-06-19 04:44:57 UTC 
Of course, the OS for this bug report should have been "Windows (all)". Sorry.
Comment 2 Ryan C. Gordon 2009-09-13 16:33:33 UTC 
Tagging this bug with "target-1.2.14" so we can try to resolve it for SDL 1.2.14.

Please note that we may choose to resolve it as WONTFIX. This tag is largely so we have a comprehensive wishlist of bugs to examine for 1.2.14 (and so we can close bugs that we'll never fix, rather than have them live forever in Bugzilla).

--ryan.
Comment 3 Sam Lantinga 2009-09-26 23:43:21 UTC 
I don't have a keyboard or layout with AltGr, and I can't find any special handling for that key in the code, it looks like Windows is supposed to treat it like RALT.

Are you seeing this problem with the current SDL snapshot?
http://www.libsdl.org/tmp/SDL-1.2.zip
Comment 4 Sam Lantinga 2009-10-17 11:07:27 UTC 
No response from the customer, I'm closing this for now.  Please reopen this as a 1.3 bug if it's an issue there.