From 2f942c9883f979615a9741b8c564215a40c8e5e4 Mon Sep 17 00:00:00 2001 From: Jack Humbert Date: Sat, 10 Jun 2017 12:23:04 -0400 Subject: [PATCH] Create Custom-Quantum-Functions.md --- docs/Custom-Quantum-Functions.md | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/Custom-Quantum-Functions.md b/docs/Custom-Quantum-Functions.md index 1c4929e5a8..0fb1c163b7 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 +```