summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorJack Humbert <jack.humb@gmail.com>2017-06-10 18:23:04 +0200
committerGitHub <noreply@github.com>2017-06-10 18:23:04 +0200
commit2f942c9883f979615a9741b8c564215a40c8e5e4 (patch)
treea50f16a420d15e9cc5069f02954fa7d8a3c1f65a /docs
parenta0ac0d3cea0390875e7baf92adede4949c2b493e (diff)
downloadqmk_firmware-2f942c9883f979615a9741b8c564215a40c8e5e4.tar.gz
qmk_firmware-2f942c9883f979615a9741b8c564215a40c8e5e4.tar.xz
Create Custom-Quantum-Functions.md
Diffstat (limited to 'docs')
-rw-r--r--docs/Custom-Quantum-Functions.md20
1 files changed, 10 insertions, 10 deletions
diff --git a/docs/Custom-Quantum-Functions.md b/docs/Custom-Quantum-Functions.md
index 1c4929e5a..0fb1c163b 100644
--- a/docs/Custom-Quantum-Functions.md
+++ b/docs/Custom-Quantum-Functions.md
@@ -4,7 +4,7 @@ A custom keyboard is about more than sending button presses to your computer. QM
We have structured QMK as a hierarchy:
-* Core
+* Core (`_quantum`)
* Keyboard/Revision (`_kb`)
* Keymap (`_user`)
@@ -64,14 +64,14 @@ The `record` variable contains infomation about the actual press:
```
keyrecord_t record {
- keyevent_t event {
- keypos_t key {
- uint8_t col
- uint8_t row
- }
- bool pressed
- uint16_t time
- }
++-keyevent_t event {
+| +-keypos_t key {
+| | +-uint8_t col
+| | +-uint8_t row
+| | }
+| +-bool pressed
+| +-uint16_t time
+| }
}
```
@@ -120,4 +120,4 @@ void led_set_kb(uint8_t usb_led) {
PORTB &= ~(1<<4);
}
}
-``` \ No newline at end of file
+```