|
|
|
/* Kaleidoscope - Firmware for computer input devices
|
|
|
|
* Copyright (C) 2013-2018 Keyboard.io, Inc.
|
|
|
|
*
|
|
|
|
* This program is free software: you can redistribute it and/or modify it under
|
|
|
|
* the terms of the GNU General Public License as published by the Free Software
|
|
|
|
* Foundation, version 3.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful, but WITHOUT
|
|
|
|
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
|
|
|
|
* FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
|
|
|
|
* details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU General Public License along with
|
|
|
|
* this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include "kaleidoscope/Kaleidoscope.h"
|
Major redesign of the plugin and hooking interface
With this redesign, we introduce a new way to create plugins, which is easier to
extend with new hook points, provides a better interface, uses less memory, less
program space, and is a tiny bit faster too.
It all begins with `kaleidoscope::Plugin` being the base class, which provides
the hook methods plugins can implement. Plugins should be declared with
`KALEIDOSCOPE_INIT_PLUGINS` instead of `Kaleidoscope.use()`. Behind this macro
is a bit of magic (see the in-code documentation) that allows us to unroll the
hook method calls, avoid vtables, and so on. It creates an override for
`kaleidoscope::Hooks::*` methods, each of which will call the respective methods
of each initialized plugin.
With the new API come new names: all of the methods plugins can implement
received new, more descriptive names that all follow a similar pattern.
The old (dubbed V1) API still remains in place, although deprecated. One can
turn it off by setting the `KALEIDOSCOPE_ENABLE_V1_PLUGIN_API` define to zero,
while compiling the firmware.
This work is based on #276, written by @noseglasses. @obra and @algernon did
some cleaning up and applied a little naming treatment.
Signed-off-by: noseglasses <shinynoseglasses@gmail.com>
Signed-off-by: Jesse Vincent <jesse@keyboard.io>
Signed-off-by: Gergely Nagy <algernon@keyboard.io>
7 years ago
|
|
|
#include "kaleidoscope/hooks.h"
|
|
|
|
#include "kaleidoscope/plugin.h"
|
|
|
|
|
|
|
|
static bool handleSyntheticKeyswitchEvent(Key mappedKey, uint8_t keyState) {
|
|
|
|
if (mappedKey.flags & RESERVED)
|
|
|
|
return false;
|
|
|
|
|
|
|
|
if (!(mappedKey.flags & SYNTHETIC))
|
|
|
|
return false;
|
|
|
|
|
|
|
|
if (mappedKey.flags & IS_CONSUMER) {
|
|
|
|
if (keyIsPressed(keyState))
|
|
|
|
kaleidoscope::hid::pressConsumerControl(mappedKey);
|
|
|
|
} else if (mappedKey.flags & IS_SYSCTL) {
|
|
|
|
if (keyIsPressed(keyState)) {
|
|
|
|
} else if (keyWasPressed(keyState)) {
|
|
|
|
kaleidoscope::hid::pressSystemControl(mappedKey);
|
|
|
|
kaleidoscope::hid::releaseSystemControl(mappedKey);
|
|
|
|
}
|
|
|
|
} else if (mappedKey.flags & IS_INTERNAL) {
|
|
|
|
return false;
|
|
|
|
} else if (mappedKey.flags & SWITCH_TO_KEYMAP) {
|
|
|
|
// Should not happen, handled elsewhere.
|
|
|
|
}
|
|
|
|
|
|
|
|
return true;
|
|
|
|
}
|
key_events: A way to hook into the event handling
This adds a new `handle_user_key_event` function, that will get called
before anything else, and can override what happens. If it returns true,
the event will not be processed further by the firmware. By default,
this function returns false, and is a no-op.
It is defined with a `weak` attribute, to let the linker know that any
other function with the same name should override his one. This makes it
possible to have another version of this function in a firmware Sketch,
and override the behaviour, to extend the event handling.
This is the foundation that allows it to use external libraries, and tap
into the firmware's event handler, to add new stuff. (We can already
hook into the main loop by changing the top `loop` function in the
Sketch)
This addresses #21 for the most part.
Signed-off-by: Gergely Nagy <algernon@madhouse-project.org>
8 years ago
|
|
|
|
|
|
|
static bool handleKeyswitchEventDefault(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) {
|
|
|
|
handleSyntheticKeyswitchEvent(mappedKey, keyState);
|
|
|
|
} else if (keyToggledOn(keyState)) {
|
|
|
|
kaleidoscope::hid::pressKey(mappedKey);
|
|
|
|
} else if (keyIsPressed(keyState)) {
|
|
|
|
kaleidoscope::hid::pressKey(mappedKey, false);
|
|
|
|
} else if (keyToggledOff(keyState) && (keyState & INJECTED)) {
|
|
|
|
kaleidoscope::hid::releaseKey(mappedKey);
|
|
|
|
}
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
void handleKeyswitchEvent(Key mappedKey, byte row, byte col, uint8_t keyState) {
|
|
|
|
/* These first steps are only done for keypresses that have a real (row,col).
|
|
|
|
* In particular, doing them for keypresses with out-of-bounds (row,col)
|
|
|
|
* would cause out-of-bounds array accesses in Layer.lookup(),
|
|
|
|
* Layer.updateLiveCompositeKeymap(), etc.
|
|
|
|
* Note that many INJECTED keypresses use the UNKNOWN_KEYSWITCH_LOCATION macro
|
|
|
|
* which gives us row==255, col==255 here. Therefore, it's legitimate that
|
|
|
|
* we may have keypresses with out-of-bounds (row, col).
|
|
|
|
* However, some INJECTED keypresses do have valid (row, col) if they are
|
|
|
|
* injecting an event tied to a physical keyswitch - and we want them to go
|
|
|
|
* through this lookup.
|
|
|
|
* So we can't just test for INJECTED here, we need to test the row and col
|
|
|
|
* directly.
|
|
|
|
* Note also that this (row, col) test avoids out-of-bounds accesses in *core*,
|
|
|
|
* but doesn't guarantee anything about event handlers - event handlers may
|
|
|
|
* still receive out-of-bounds (row, col), and handling that properly is on
|
|
|
|
* them.
|
|
|
|
*/
|
|
|
|
if (row < ROWS && col < COLS) {
|
|
|
|
|
|
|
|
/* If a key had an on event, we update the live composite keymap. See
|
|
|
|
* layers.h for an explanation about the different caches we have. */
|
|
|
|
if (keyToggledOn(keyState)) {
|
|
|
|
if (mappedKey.raw == Key_NoKey.raw) {
|
|
|
|
Layer.updateLiveCompositeKeymap(row, col);
|
|
|
|
} else {
|
|
|
|
Layer.updateLiveCompositeKeymap(row, col, mappedKey);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* If the key we are dealing with is masked, ignore it until it is released.
|
|
|
|
* When releasing it, clear the mask, so future key events can be handled
|
|
|
|
* appropriately.
|
|
|
|
*
|
|
|
|
* See layers.cpp for an example that masks keys, and the reason why it does
|
|
|
|
* so.
|
|
|
|
*/
|
|
|
|
if (KeyboardHardware.isKeyMasked(row, col)) {
|
|
|
|
if (keyToggledOff(keyState)) {
|
|
|
|
KeyboardHardware.unMaskKey(row, col);
|
|
|
|
} else {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Convert (row, col) to the correct mappedKey
|
|
|
|
* The condition here means that if mappedKey and (row, col) are both valid,
|
|
|
|
* the mappedKey wins - we don't re-look-up the mappedKey
|
|
|
|
*/
|
|
|
|
if (mappedKey.raw == Key_NoKey.raw) {
|
|
|
|
mappedKey = Layer.lookup(row, col);
|
|
|
|
}
|
|
|
|
|
|
|
|
} // row < ROWS && col < COLS
|
|
|
|
|
|
|
|
// Keypresses with out-of-bounds (row,col) start here in the processing chain
|
|
|
|
|
Major redesign of the plugin and hooking interface
With this redesign, we introduce a new way to create plugins, which is easier to
extend with new hook points, provides a better interface, uses less memory, less
program space, and is a tiny bit faster too.
It all begins with `kaleidoscope::Plugin` being the base class, which provides
the hook methods plugins can implement. Plugins should be declared with
`KALEIDOSCOPE_INIT_PLUGINS` instead of `Kaleidoscope.use()`. Behind this macro
is a bit of magic (see the in-code documentation) that allows us to unroll the
hook method calls, avoid vtables, and so on. It creates an override for
`kaleidoscope::Hooks::*` methods, each of which will call the respective methods
of each initialized plugin.
With the new API come new names: all of the methods plugins can implement
received new, more descriptive names that all follow a similar pattern.
The old (dubbed V1) API still remains in place, although deprecated. One can
turn it off by setting the `KALEIDOSCOPE_ENABLE_V1_PLUGIN_API` define to zero,
while compiling the firmware.
This work is based on #276, written by @noseglasses. @obra and @algernon did
some cleaning up and applied a little naming treatment.
Signed-off-by: noseglasses <shinynoseglasses@gmail.com>
Signed-off-by: Jesse Vincent <jesse@keyboard.io>
Signed-off-by: Gergely Nagy <algernon@keyboard.io>
7 years ago
|
|
|
// New event handler interface
|
|
|
|
if (kaleidoscope::Hooks::onKeyswitchEvent(mappedKey, row, col, keyState) != kaleidoscope::EventHandlerResult::OK)
|
|
|
|
return;
|
|
|
|
|
|
|
|
mappedKey = Layer.eventHandler(mappedKey, row, col, keyState);
|
|
|
|
if (mappedKey.raw == Key_NoKey.raw)
|
|
|
|
return;
|
|
|
|
handleKeyswitchEventDefault(mappedKey, row, col, keyState);
|
|
|
|
}
|