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
Ignore custom keyboard scan codes #3468
Comments
Comment 1 by Brendon22 on 2013-08-25 07:12 A Notebook that does this. Is the HP ProBook 4340s just for the record. |
Comment 3 by James Teh <jamie@... on 2013-08-26 01:00
|
Comment 4 by James Teh <jamie@... on 2013-08-26 01:03
Changes:
|
Comment 6 by ondrosik on 2013-08-27 19:33 |
Comment 7 by jteh on 2013-08-28 00:30 |
Comment 8 by ondrosik on 2013-08-28 08:56 |
Comment 9 by James Teh <jamie@... on 2013-08-29 03:44
|
Comment 10 by James Teh <jamie@... on 2013-08-29 03:45
|
Comment 11 by ondrosik on 2013-09-03 05:31 |
Comment 12 by Michael Curran <mick@... on 2013-09-16 23:51
Changes:
|
Comment 13 by mdcurran on 2013-09-16 23:51 |
Reported by jteh on 2013-08-25 01:37
Some computer manufacturers use custom keyboard scan codes to indicate custom buttons or other behaviour; e.g. wireless toggle, screen brightness, gyroscope movement, etc. This causes multiple issues:
From what I've been able to determine, these custom scan codes have no vk code mapping, so they get a vk code of 0xff. If they have no vk code, this should mean Windows doesn't know about them, in which case we almost certainly don't care about them.
Therefore, we should ignore key presses with a vk code of 0xff. I haven't decided whether we should just avoid generating gestures for them altogether or whether we should generate gestures but avoid silencing speech and give them a name which indicates they are unknown.
The text was updated successfully, but these errors were encountered: