From bb53635f33c213e5a940edea8b07026ef89aed42 Mon Sep 17 00:00:00 2001 From: fauxpark Date: Sat, 9 Dec 2017 16:56:58 +1100 Subject: Trim trailing whitespace --- docs/quantum_keycodes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/quantum_keycodes.md') diff --git a/docs/quantum_keycodes.md b/docs/quantum_keycodes.md index 4b7ee9384..1d7fc0e12 100644 --- a/docs/quantum_keycodes.md +++ b/docs/quantum_keycodes.md @@ -2,7 +2,7 @@ Quantum keycodes allow for easier customisation of your keymap than the basic ones provide, without having to define custom actions. -All keycodes within quantum are numbers between `0x0000` and `0xFFFF`. Within your `keymap.c` it may look like you have functions and other special cases, but ultimately the C preprocessor will translate those into a single 4 byte integer. QMK has reserved `0x0000` through `0x00FF` for standard keycodes. These are keycodes such as `KC_A`, `KC_1`, and `KC_LCTL`, which are basic keys defined in the USB HID specification. +All keycodes within quantum are numbers between `0x0000` and `0xFFFF`. Within your `keymap.c` it may look like you have functions and other special cases, but ultimately the C preprocessor will translate those into a single 4 byte integer. QMK has reserved `0x0000` through `0x00FF` for standard keycodes. These are keycodes such as `KC_A`, `KC_1`, and `KC_LCTL`, which are basic keys defined in the USB HID specification. On this page we have documented keycodes between `0x00FF` and `0xFFFF` which are used to implement advanced quantum features. If you define your own custom keycodes they will be put into this range as well. -- cgit v1.2.3-24-g4f1b