| Summary: | Spacebar not responding | ||
|---|---|---|---|
| Product: | SDL | Reporter: | kongr45gpen <electrovesta> |
| Component: | video | Assignee: | Sam Lantinga <slouken> |
| Status: | RESOLVED FIXED | QA Contact: | Sam Lantinga <slouken> |
| Severity: | major | ||
| Priority: | P2 | CC: | alex, kubissus, sezeroz |
| Version: | HG 2.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Attachments: |
Experimental patch to correct groups sent to XkbKeycodeToKeysym
Patch to correct XkbKeycodeToKeysym groups v2 Patch to correct XkbKeycodeToKeysym groups v3 |
||
|
Description
kongr45gpen
2015-09-26 21:36:04 UTC
I can't personally reproduce this, but it might be that the group obtained from XkbGetState is out of range for the call to XkbKeycodeToKeysym for that particular (space) key. I think we're supposed to check XkbKeyGroupInfo + XkbKeyNumGroups and manually correct the group before calling XkbKeyCodeToKeysym. Atleast that's what this stackoverflow answer seems to suggest: http://stackoverflow.com/a/10233743 It seems really weird that XkbKeycodeToKeysym wouldn't do that internally though... The call to XkbKeycodeToKeysym does return NoSymbol for me, suggesting that the group is out of range for that key. Created attachment 2280 [details]
Experimental patch to correct groups sent to XkbKeycodeToKeysym
Try this patch, hopefully it will fix the problem.
Yup, the patch has fixed the issue, thanks! Created attachment 2282 [details]
Patch to correct XkbKeycodeToKeysym groups v2
Here's a better version of the patch that only remaps the group if it was actually out of range.
Created attachment 2283 [details]
Patch to correct XkbKeycodeToKeysym groups v3
I was using XkbOutOfRangeGroupInfo instead of XkbOutOfRangeGroupNumber in the last patches, this one fixes that.
Hopefully this one does everything as it should, kinda hard to know since the documentation on this stuff is pretty much non-existent.
Fixed, thanks! https://hg.libsdl.org/SDL/rev/0426a82e291d |