You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
130 lines
5.4 KiB
130 lines
5.4 KiB
# Kaleidoscope-Qukeys
|
|
|
|
![status][st:experimental] [![Build Status][travis:image]][travis:status]
|
|
|
|
[travis:image]: https://travis-ci.org/keyboardio/Kaleidoscope-Qukeys.svg?branch=master
|
|
[travis:status]: https://travis-ci.org/keyboardio/Kaleidoscope-Qukeys
|
|
|
|
[st:stable]: https://img.shields.io/badge/stable-✔-black.svg?style=flat&colorA=44cc11&colorB=494e52
|
|
[st:broken]: https://img.shields.io/badge/broken-X-black.svg?style=flat&colorA=e05d44&colorB=494e52
|
|
[st:experimental]: https://img.shields.io/badge/experimental----black.svg?style=flat&colorA=dfb317&colorB=494e52
|
|
|
|
## Concept
|
|
|
|
This Kaleidoscope plugin allows you to overload keys on your keyboard so that they produce
|
|
one keycode (i.e. symbol) when tapped, and a different keycode -- most likely a modifier
|
|
(e.g. `shift` or `alt`) -- when held.
|
|
|
|
|
|
## Setup
|
|
|
|
- Include the header file:
|
|
```
|
|
#include <Kaleidoscope-Qukeys.h>
|
|
```
|
|
- Use the plugin in the `KALEIDOSCOPE_INIT_PLUGINS` macro:
|
|
```
|
|
KALEIDOSCOPE_INIT_PLUGINS(Qukeys);
|
|
```
|
|
- Define some `Qukeys` of the format `Qukey(layer, row, col, alt_keycode)` (layers, rows and columns are all zero-indexed, rows are top to bottom and columns are left to right):
|
|
```
|
|
QUKEYS(
|
|
kaleidoscope::Qukey(0, 2, 1, Key_LeftGui), // A/cmd
|
|
kaleidoscope::Qukey(0, 2, 2, Key_LeftAlt), // S/alt
|
|
kaleidoscope::Qukey(0, 2, 3, Key_LeftControl), // D/ctrl
|
|
kaleidoscope::Qukey(0, 2, 4, Key_LeftShift) // F/shift
|
|
)
|
|
```
|
|
|
|
`Qukeys` will work best if it's the first plugin in the `use()` list, because when typing
|
|
overlap occurs, it will (temporarily) mask keys and block them from being processed by
|
|
other plugins. If those other plugins handle the keypress events first, it may not work as
|
|
expected. It doesn't _need_ to be first, but if it's `use()`'d after another plugin that
|
|
handles typing events, especially one that sends extra keyboard HID reports, it is more
|
|
likely to generate errors and out-of-order events.
|
|
|
|
|
|
## Configuration
|
|
|
|
- set timeout
|
|
|
|
- activate/deactivate `Qukeys`
|
|
|
|
- see the
|
|
[example](https://github.com/keyboardio/Kaleidoscope-Qukeys/blob/master/examples/Qukeys/Qukeys.ino)
|
|
for a way to turn `Qukeys` on and off, using Kaleidoscope-Macros
|
|
|
|
### DualUse key definitions
|
|
|
|
In addition to normal `Qukeys` described above, Kaleidoscope-Qukeys also treats
|
|
DualUse keys in the keymap as `Qukeys`. This makes `Qukeys` a drop-in replacement
|
|
for the `DualUse` plugin, without the need to edit the keymap.
|
|
|
|
|
|
The plugin provides a number of macros one can use in keymap definitions:
|
|
|
|
#### `CTL_T(key)`
|
|
|
|
> A key that acts as the *left* `Control` when held, or used in conjunction with
|
|
> other keys, but as `key` when tapped in isolation. The `key` argument must be
|
|
> a plain old key, and can't have any modifiers or anything else applied.
|
|
|
|
#### `ALT_T(key)`
|
|
|
|
> A key that acts as the *left* `Alt` when held, or used in conjunction with
|
|
> other keys, but as `key` when tapped in isolation. The `key` argument must be
|
|
> a plain old key, and can't have any modifiers or anything else applied.
|
|
|
|
#### `SFT_T(key)`
|
|
|
|
> A key that acts as the *left* `Shift` when held, or used in conjunction with
|
|
> other keys, but as `key` when tapped in isolation. The `key` argument must be
|
|
> a plain old key, and can't have any modifiers or anything else applied.
|
|
|
|
#### `GUI_T(key)`
|
|
|
|
> A key that acts as the *left* `GUI` when held, or used in conjunction with
|
|
> other keys, but as `key` when tapped in isolation. The `key` argument must be
|
|
> a plain old key, and can't have any modifiers or anything else applied.
|
|
|
|
#### `MT(mod, key)`
|
|
|
|
> A key that acts as `mod` when held, or used in conjunction with other keys,
|
|
> but as `key` when tapped in isolation. The `key` argument must be a plain old
|
|
> key, and can't have any modifiers or anything else applied. The `mod` argument
|
|
> can be any of the modifiers, *left* or *right* alike.
|
|
|
|
#### `LT(layer, key)`
|
|
|
|
> A key that momentarily switches to `layer` when held, or used in conjunction
|
|
> with other keys, but as `key` when tapped in isolation. The `key` argument
|
|
> must be a plain old key, and can't have any modifiers or anything else
|
|
> applied.
|
|
|
|
## Design & Implementation
|
|
|
|
When a `Qukey` is pressed, it doesn't immediately add a corresponding keycode to the HID
|
|
report; it adds that key to a queue, and waits until one of three things happens:
|
|
|
|
1. a time limit is reached
|
|
|
|
2. the `Qukey` is released
|
|
|
|
3. a subsequently-pressed key is released
|
|
|
|
Until one of those conditions is met, all subsequent keypresses are simply added to the
|
|
queue, and no new reports are sent to the host. Once a condition is met, the `Qukey` is
|
|
flushed from the queue, and so are any subsequent keypresses (up to, but not including,
|
|
the next `Qukey` that is still pressed).
|
|
|
|
Basically, if you hold the `Qukey`, then press and release some other key, you'll get the
|
|
alternate keycode (probably a modifier) for the `Qukey`, even if you don't wait for a
|
|
timeout. If you're typing quickly, and there's some overlap between two keypresses, you
|
|
won't get the alternate keycode, and the keys will be reported in the order that they were
|
|
pressed -- as long as the keys are released in the same order they were pressed.
|
|
|
|
The time limit is mainly there so that a `Qukey` can be used as a modifier (in its
|
|
alternate state) with a second input device (e.g. a mouse). It can be quite short (200ms
|
|
is probably short enough) -- as long as your "taps" while typing are shorter than the time
|
|
limit, you won't get any unintended alternate keycodes.
|