6 Commits (6bd1f81ea003e5f154c4caecfb172cb715c004bf)

Author	SHA1	Message	Date
Michael Richters	83a0037971	Use Qukeys min prior interval only after printable characters ... Some users have pointed out that certain keys (in particular, `space` & `backspace`) are inconvenient to require the minimum prior interval to make a qukey resolve to a modifier (especially `shift`). We could blacklist those keys, but it's hard to predict what they all might be. The problem is mainly one for very fast typists, and therefore I expect it to show up when following the "normal" printable keys, not often other keys. This could also be made into a configurable list, but I'd prefer not to do so unless there's serious demand for it, as Qukeys already has too many settings. Signed-off-by: Michael Richters <gedankenexperimenter@gmail.com>	4 years ago
Michael Richters	32aa6374ec	Improve Qukeys protection against unintended modifiers ... Unintended modifiers are becoming an increasingly big problem among users of Qukeys. This change adds yet another configuration option to prevent this from happening while users are typing fast. It introduces a new requirement to make a qukey eligible to become a qukey; a minimum amount of time that must pass between the keypress event for a non-modifier key and the subsequent keypress event of the qukey. Signed-off-by: Michael Richters <gedankenexperimenter@gmail.com>	4 years ago
Gergely Nagy	8d4dfa877b	Deprecate the key masking API ... Key masking was a bandaid, and we have better ways to achieve the same thing now. All current users have been switched over to different methods now, so lets deprecate the masking. We only put the `DEPRECATED` label on the `maskKey` method, because the rest are used internally too, and we do not want to emit warnings for those. Fixes #884. Signed-off-by: Gergely Nagy <algernon@keyboard.io>	4 years ago
Jesse Vincent	2c9d3747ec	Working toward being able to have a coherent organization of our docs	5 years ago
Gergely Nagy	6689912bcd	LEDControl: Add disable/enable functions, and a toggle key ... This adds `LEDControl.disable()` and `LEDControl.enable()` which disable and enable LED operations, respectively. These are meant to replace the current `LEDControl.paused` property (which is getting deprecated with this change), and do some additional work on top of just disabling or re-enabling future updates and sync. Namely, `disable()` will also turn LEDs off, while `enable()` will refresh them all, too. We also add a dedicated `Key_LEDToggle` key to disable/enable LEDs. This is useful when one wants to turn LEDs off, without changing active LED mode to `LEDOff`. Signed-off-by: Gergely Nagy <algernon@keyboard.io>	5 years ago
Jesse Vincent	d3e0252a75	move news into docs directory, fix examples copy	5 years ago