From d9363b37815279e5004106345d93f19d584db2a2 Mon Sep 17 00:00:00 2001 From: Tycho Andersen Date: Sat, 8 Dec 2018 14:43:32 -0700 Subject: wrap the *super* long lines I hate to be that guy, but I was reading these on github's page when deciding whether or not to order a keyboard.io, and the extra long lines here are not automatically wrapped when browsing the repo on github. Signed-off-by: Tycho Andersen --- Model01-Firmware.ino | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/Model01-Firmware.ino b/Model01-Firmware.ino index b6a556c..66701a5 100644 --- a/Model01-Firmware.ino +++ b/Model01-Firmware.ino @@ -412,17 +412,21 @@ KALEIDOSCOPE_INIT_PLUGINS( // interface through which the keymap in EEPROM can be edited. Focus, - // FocusSettingsCommand adds a few Focus commands, intended to aid in changing some settings of the keyboard, such as the default layer (via the `settings.defaultLayer` command) + // FocusSettingsCommand adds a few Focus commands, intended to aid in + // changing some settings of the keyboard, such as the default layer (via the + // `settings.defaultLayer` command) FocusSettingsCommand, // FocusEEPROMCommand adds a set of Focus commands, which are very helpful in // both debugging, and in backing up one's EEPROM contents. FocusEEPROMCommand, - // The boot greeting effect pulses the LED button for 10 seconds after the keyboard is first connected + // The boot greeting effect pulses the LED button for 10 seconds after the + // keyboard is first connected BootGreetingEffect, - // The hardware test mode, which can be invoked by tapping Prog, LED and the left Fn button at the same time. + // The hardware test mode, which can be invoked by tapping Prog, LED and the + // left Fn button at the same time. TestMode, // LEDControl provides support for other LED modes -- cgit v1.2.3 From 852566ee1c0d79643ea2940bd769757fb6d72a0c Mon Sep 17 00:00:00 2001 From: Tycho Andersen Date: Sun, 9 Dec 2018 11:04:58 -0700 Subject: add a blurb about binding the PROG key to things Signed-off-by: Tycho Andersen --- Model01-Firmware.ino | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/Model01-Firmware.ino b/Model01-Firmware.ino index 66701a5..951e24c 100644 --- a/Model01-Firmware.ino +++ b/Model01-Firmware.ino @@ -108,9 +108,15 @@ enum { MACRO_VERSION_INFO, * using ___ to let keypresses fall through to the previously active layer * using XXX to mark a keyswitch as 'blocked' on this layer * using ShiftToLayer() and LockLayer() keys to change the active keymap. - * the special nature of the PROG key * keeping NUM and FN consistent and accessible on all layers * + * The PROG key is special, since it is how you indicate to the board that you + * want to flash the firmware. However, it can be remapped to a regular key. + * When the keyboard boots, it first looks to see whether the PROG key is held + * down; if it is, it simply awaits further flashing instructions. If it is + * not, it continues loading the rest of the firmware and the keyboard + * functions normally, with whatever binding you have set to PROG. More detail + * here: https://community.keyboard.io/t/how-the-prog-key-gets-you-into-the-bootloader/506/8 * * The "keymaps" data structure is a list of the keymaps compiled into the firmware. * The order of keymaps in the list is important, as the ShiftToLayer(#) and LockLayer(#) -- cgit v1.2.3