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 3076 - No key up/down message for backquote on US international keyboard
Summary: No key up/down message for backquote on US international keyboard
Status: RESOLVED DUPLICATE of bug 2071
Alias: None
Product: SDL
Classification: Unclassified
Component: events (show other bugs)
Version: 2.0.3
Hardware: x86_64 Linux
: P2 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-27 20:43 UTC by Drew Bliss
Modified: 2015-12-31 05:01 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Drew Bliss 2015-07-27 20:43:23 UTC 
If I’m using a regular US English keyboard layout I get key up/down for ` and everything works as expected.  If I switch to a US alternative international English keyboard layout then no key up/down is generated.  A ` character event still comes through but no up/down.  In the user report that prompted me trying this the user says that ` is a modifier key to get accents so maybe that’s why it isn’t coming through?  The lack of up/down events for the key means that users cannot bind it to an action and losing a useful key seems undesirable.
 
https://github.com/ValveSoftware/Dota-2-Reborn/issues/268
Comment 1 Daniel Gibson 2015-12-30 22:24:56 UTC 
This is probably a duplicate of https://bugzilla.libsdl.org/show_bug.cgi?id=2071 related to https://bugzilla.libsdl.org/show_bug.cgi?id=2526
Comment 2 Ryan C. Gordon 2015-12-31 05:01:21 UTC 
(In reply to Daniel Gibson from comment #1)
> This is probably a duplicate of
> https://bugzilla.libsdl.org/show_bug.cgi?id=2071

Agreed, let's work out of that bug report, because it has more content in it.

--ryan.

*** This bug has been marked as a duplicate of bug 2071 ***