Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keyboard event doesn't return sym value when "nonusbackslash" key is pressed #3476

Closed
SDLBugzilla opened this issue Feb 11, 2021 · 1 comment
Labels
abandoned Bug has been abandoned for various reasons

Comments

@SDLBugzilla
Copy link
Collaborator

This bug report was migrated from our old Bugzilla tracker.

Reported in version: 2.0.10
Reported for operating system, platform: Linux, ARM

Comments on the original bug report:

On 2019-12-10 19:01:55 +0000, rosenrost wrote:

I am running Hatari, an Atari ST emulator, on my Raspberry Pi 3B. Hatari uses SDL2 in order to display graphics without X11. I am using a German keyboard which has a key next to the left shift key that is missing on US keyboard layouts. This key is not recognized by Hatari.

After adding some debug messages to Hataris keyboard handling functions, I discoverd that the keyboard event returns 0 in the sym field of the SDL_keysym structure, while the correct scan code (100) is returned in the scancode field of that structure.

In my case (German keyboard layout, but it's the same on any western European keyboard except UK), the the characters "<" and ">" are mapped to this key, so I really need it. So, SDL_keysym.sym should be 60 and not 0.

On 2019-12-11 15:23:53 +0000, rosenrost wrote:

Oh, I forgot to mention that the RPI driver is used.

@slouken slouken removed the bug label May 11, 2022
@slouken slouken added the abandoned Bug has been abandoned for various reasons label Nov 6, 2023
@slouken
Copy link
Collaborator

slouken commented Nov 6, 2023

SDL 2.0 is now in maintenance mode, and all inactive issues are being closed. If this issue is impacting you, please feel free to reopen it with additional information.

@slouken slouken closed this as not planned Won't fix, can't repro, duplicate, stale Nov 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
abandoned Bug has been abandoned for various reasons
Projects
None yet
Development

No branches or pull requests

2 participants