From 49b16ebc8ff03cdb8d2f3e822759328979d490ba Mon Sep 17 00:00:00 2001 From: Vasily Date: Mon, 22 Apr 2019 20:35:02 +0200 Subject: [PATCH] Remove F10, F11 and F12 function keys from keyboard spec 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. --- docs/specs/Keyboard_Manager-Parser_Spec.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/specs/Keyboard_Manager-Parser_Spec.txt b/docs/specs/Keyboard_Manager-Parser_Spec.txt index 2fd39c6..ef97c4e 100644 --- a/docs/specs/Keyboard_Manager-Parser_Spec.txt +++ b/docs/specs/Keyboard_Manager-Parser_Spec.txt @@ -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.