Kaleidoscope

Author	SHA1	Message	Date
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