SteamFrame/OpenVR-AdvancedSettings-frame
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove F10, F11 and F12 function keys from keyboard spec

Browse Source 
There is no way to tell if they are meant to be one or two keys and in
this case simplicity of use wins out.
This commit is contained in:
Vasily
2019-05-25 18:49:42 +02:00
committed by username223
parent d2127e53aa
commit 49b16ebc8f
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/specs/Keyboard_Manager-Parser_Spec.txt
+3 -1
View File
@@ -47,7 +47,7 @@ A token is either a modifier symbol, literal symbol, symbol sequence or space ch
|---|---|
| A to Z | The letter in lowercase. `a`, `b`, `c`, ... |
| Number Row 0-9 | The number. `0`, `1`, `2`, ... |
| Function keys F1-F12 | Capital F followed by number. `F1`, `F2`, `F3`, ... |
| Function keys F1-F9 | Capital F followed by number. `F1`, `F2`, `F3`, ... |
| Backspace | `BACKSPACE` |
| Space | `SPACE` |
| Tab | `TAB` |
@@ -98,6 +98,8 @@ There is no limit on the length of the string.
If a specific key is not supported on a platform, triggering that key is a no-op. A log message may be displayed.
Only F1 through F9 is supported. This is because there is no way to tell if `F12` is meant to be `F1+, F1-, 2+, 2-` or `F12+, F12-`.
Whether A on AZERTY keyboards triggers A or Q is undefined.
Anything to do with unsupported keyboard locales is undefined.