Adapt Qukeys to keyboard state array

When Qukeys stops event processing from its `onKeyswitchEvent()` handler, it's
because the event should be treated as non-existent (in most cases, it's merely
delayed). This keeps the keyboard state array from getting updated, as well as
completely stopping event processing.

Signed-off-by: Michael Richters <gedankenexperimenter@gmail.com>
pull/1024/head
Michael Richters 4 years ago
parent 9d06843bd2
commit 081ca52c91
No known key found for this signature in database
GPG Key ID: 1288FD13E4EEF0C0

@ -72,7 +72,7 @@ EventHandlerResult Qukeys::onKeyswitchEvent(Key& key, KeyAddr k, uint8_t key_sta
} }
// Any event that gets added to the queue gets re-processed later, so we // Any event that gets added to the queue gets re-processed later, so we
// need to abort processing now. // need to abort processing now.
return EventHandlerResult::EVENT_CONSUMED; return EventHandlerResult::ABORT;
} }
// The key is being held. We need to determine if we should block it because // The key is being held. We need to determine if we should block it because
@ -89,7 +89,7 @@ EventHandlerResult Qukeys::onKeyswitchEvent(Key& key, KeyAddr k, uint8_t key_sta
} }
// Otherwise, the first matching event was a key press, so we need to // Otherwise, the first matching event was a key press, so we need to
// suppress it for now. // suppress it for now.
return EventHandlerResult::EVENT_CONSUMED; return EventHandlerResult::ABORT;
} }
} }

Loading…
Cancel
Save