change "handle_key_event" to "handle_keyswitch_event" to make it clear that we're talking about something on the physical layer, rather than, say, a HID event

src/Kaleidoscope.cpp

@@ -15,7 +15,7 @@ Kaleidoscope_::setup(void) {
     KeyboardHardware.setup();
 
     // A workaround, so that the compiler does not optimize this out...
-    handle_key_event (Key_NoKey, 255, 255, 0);
+    handle_keyswitch_event (Key_NoKey, 255, 255, 0);
 }
 
 void

src/key_events.cpp

@@ -1,6 +1,6 @@
 #include "Kaleidoscope.h"
 
-static bool handle_synthetic_key_event(Key mappedKey, uint8_t keyState) {
+static bool handle_synthetic_keyswitch_event(Key mappedKey, uint8_t keyState) {
     if (mappedKey.flags & RESERVED)
         return false;
 
@@ -26,12 +26,12 @@ static bool handle_synthetic_key_event(Key mappedKey, uint8_t keyState) {
     return true;
 }
 
-static bool handle_key_event_default(Key mappedKey, byte row, byte col, uint8_t keyState) {
+static bool handle_keyswitch_event_default(Key mappedKey, byte row, byte col, uint8_t keyState) {
     //for every newly pressed button, figure out what logical key it is and send a key down event
     // for every newly released button, figure out what logical key it is and send a key up event
 
     if (mappedKey.flags & SYNTHETIC) {
-        handle_synthetic_key_event( mappedKey, keyState);
+        handle_synthetic_keyswitch_event( mappedKey, keyState);
     } else if (key_is_pressed(keyState)) {
         press_key(mappedKey);
     } else if (key_toggled_off(keyState) && (keyState & INJECTED)) {
@@ -79,7 +79,7 @@ void release_key(Key mappedKey) {
     Keyboard.release(mappedKey.keyCode);
 }
 
-void handle_key_event(Key mappedKey, byte row, byte col, uint8_t keyState) {
+void handle_keyswitch_event(Key mappedKey, byte row, byte col, uint8_t keyState) {
     if (!(keyState & INJECTED)) {
         mappedKey = Layer.lookup(row, col);
     }
@@ -92,5 +92,5 @@ void handle_key_event(Key mappedKey, byte row, byte col, uint8_t keyState) {
     mappedKey = Layer.eventHandler(mappedKey, row, col, keyState);
     if (mappedKey.raw == Key_NoKey.raw)
         return;
-    handle_key_event_default(mappedKey, row, col, keyState);
+    handle_keyswitch_event_default(mappedKey, row, col, keyState);
 }

src/key_events.h

@@ -14,13 +14,13 @@ extern const Key keymaps[][ROWS][COLS];
 #define UNKNOWN_KEYSWITCH_LOCATION 255,255
 
 // sending events to the computer
-/* The event handling starts with the Scanner calling handle_key_event() for
+/* The event handling starts with the Scanner calling handle_keyswitch_event() for
  * every key in the matrix, and it is the task of this method to figure out what
  * to do, it is the main entry point.
  *
  * This function will iterate through an array of handler functions, and stop as
  * soon as one of them signals that the event has been handled. To make it
- * possible to inject synthetic events, one can call handle_key_event from
+ * possible to inject synthetic events, one can call handle_keyswitch_event from
  * within a custom handler (making the event handling recursive), with a
  * different keycode.
  *
@@ -29,20 +29,20 @@ extern const Key keymaps[][ROWS][COLS];
  * normal modifier instead. In this case, the keymap would contain a key with
  * OSM flags set, and the event handler would remove the OSM flags, and let the
  * system handle the key as it would have, without the OSM flags. So we simply
- * clear the flags, and call handle_key_event again, with the modifier keycode
+ * clear the flags, and call handle_keyswitch_event again, with the modifier keycode
  * as the first argument. This way, we could insert an event, and have the whole
  * chain re-process it, instead of registering the keycode ourselves with HID
  * ourselves. Injecting allows any and all custom handlers to have a chance,
  * too.
  *
- * For this reason, the handle_key_event receives four arguments: the mapped key
+ * For this reason, the handle_keyswitch_event receives four arguments: the mapped key
  * (or Key_NoKey if we do not want to override what is in the keymap), the row
  * and column of the key, so we can look up the code for it, and the current and
  * previous state of the key, so we can determine what the event is. The
  * currentState may be flagged INJECTED, which signals that the event was
  * injected, and is not a direct result of a keypress, coming from the scanner.
  */
-void handle_key_event(Key mappedKey, byte row, byte col, uint8_t keyState);
+void handle_keyswitch_event(Key mappedKey, byte row, byte col, uint8_t keyState);
 
 // Internal use
 void press_key(Key mappedKey);

src/layers.cpp

@@ -7,7 +7,7 @@ uint8_t Layer_::highestLayer;
 uint8_t Layer_::keyMap[ROWS][COLS];
 Key (*Layer_::getKey)(uint8_t layer, byte row, byte col) = Layer.getKeyFromPROGMEM;
 
-static void handle_keymap_key_event(Key keymapEntry, uint8_t keyState) {
+static void handle_keymap_keyswitch_event(Key keymapEntry, uint8_t keyState) {
     if (keymapEntry.keyCode >= MOMENTARY_OFFSET) {
         uint8_t target = keymapEntry.keyCode - MOMENTARY_OFFSET;
 
@@ -44,7 +44,7 @@ Layer_::eventHandler(Key mappedKey, byte row, byte col, uint8_t keyState) {
     if (mappedKey.flags != (SYNTHETIC | SWITCH_TO_KEYMAP))
         return mappedKey;
 
-    handle_keymap_key_event(mappedKey, keyState);
+    handle_keymap_keyswitch_event(mappedKey, keyState);
     return Key_NoKey;
 }