8 Commits (c60dd9526df3b835fb8b2d57d65d625ea4e3db85)

Author	SHA1	Message	Date
Michael Richters	6e2f3e8843	Include `stdint.h` in Kaleidoscope-Ranges.h ... This makes it unnecessary to include `Arduino.h` (or `stdint.h`, or some other header that includes it) before including Kaleidoscope-Ranges.h. Signed-off-by: Michael Richters <gedankenexperimenter@gmail.com>	4 years ago
Michael Richters	58f56236a1	Add `OneShot_ActiveStickyKey` ... This key makes any held key (or otherwise active key, most likely OneShot keys) sticky when it toggles on. Signed-off-by: Michael Richters <gedankenexperimenter@gmail.com>	4 years ago
Michael Richters	af19a43146	Add `OneShot_MetaStickyKey` ... This is a special OneShot key that makes any subsequently-pressed key sticky, regardless of its value. Signed-off-by: Michael Richters <gedankenexperimenter@gmail.com>	4 years ago
Michael Richters	6dd77b96c4	Allow user to customize which key will cancel one-shot keys ... Signed-off-by: Michael Richters <gedankenexperimenter@gmail.com>	4 years ago
Michael Richters	c9534155e6	Clarify the Macros plugin `Key` value range ... This replaces the magic number `24576` with the old definition of the start of the Macros plugin's `Key` range, to make it clear that it will match bitwise tests for "not a plugin key" (the two high bits are both zeros) and the `SYNTHETIC` flags bit. I also elaborated on the reasons for keeping the existing `Key` values stable and added a comment addressing the more likely case where new values are being added, rather than fighting the last war and focusing only on the one legacy plugin range that exists outside the canonical plugin range, whose values have already been incorporated here. Signed-off-by: Michael Richters <gedankenexperimenter@gmail.com>	4 years ago
Gergely Nagy	4f9afcfdb9	plugins/Ranges: Add an explanatory comment above the ranges enum ... Signed-off-by: Gergely Nagy <algernon@keyboard.io>	4 years ago
Gergely Nagy	9c49d5b2ac	plugins/Ranges: Fix the Macro key ranges ... Macro keycodes pre-date the Ranges plugin, so they previously had a keycode that sorted before ranges::FIRST. For the sake of backwards compatibility, we want to keep using the same keycodes. Fixes #1010. Signed-off-by: Gergely Nagy <algernon@keyboard.io>	4 years ago
Jesse Vincent	54cae3365d	Extract Kaleidoscope-Ranges back to a plugin	4 years ago