From f7fdc13e42a47e4d99ddf5e208f6ae5776eb49f0 Mon Sep 17 00:00:00 2001 From: drashna Date: Tue, 26 Sep 2023 06:19:05 +0000 Subject: [PATCH] =?UTF-8?q?Deploying=20to=20gh-pages=20from=20@=20qmk/qmk?= =?UTF-8?q?=5Ffirmware@17ae28f0e41aa30937d80e48dc19548c76cc6e43=20?= =?UTF-8?q?=F0=9F=9A=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- feature_programmable_button.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/feature_programmable_button.md b/feature_programmable_button.md index 43a9e7fc160..091464e19c0 100644 --- a/feature_programmable_button.md +++ b/feature_programmable_button.md @@ -2,7 +2,7 @@ Programmable Buttons are keys that have no predefined meaning. This means they can be processed on the host side by custom software without the operating system trying to interpret them. -The keycodes are emitted according to the HID Telephony Device page (`0x0B`), Programmable Button usage (`0x07`). On Linux (> 5.14) they are handled automatically and translated to `KEY_MACRO#` keycodes (up to `KEY_MACRO30`). +The keycodes are emitted according to the HID Telephony Device page (`0x0B`), Programmable Button usage (`0x09`). On Linux (> 5.14) they are handled automatically and translated to `KEY_MACRO#` keycodes (up to `KEY_MACRO30`). ?> Currently there is no known support in Windows or macOS. It may be possible to write a custom HID driver to receive these usages, but this is out of the scope of the QMK documentation.