4 Commits (e950aa18303ce0280e3760b321fca6533356d219)

Author	SHA1	Message	Date
Florian Fleissner	1d7008d96f	Extracted and renamed class Kaleidoscope->Runtime ... This was done to enable separate inclusion of the central runtime class without having to include the central header kaleidoscope/Kaleidoscope.h which used to pull in a lot of stuff that is not required in many compilation units. The new class `Runtime_` lives in namespace kaleidoscope its singleton instance is `kaleidoscope::Runtime`. It is now only available internally in library Kaleidoscope but not from the sketch. The original class name `Kaleidoscope_` in global scope has been deprecated. The original instance name `Kaleidoscope` in global scope has been preserved to be used by end users in their sketches. Signed-off-by: Florian Fleissner <florian.fleissner@inpartik.de>	5 years ago
Florian Fleissner	18093e4852	Fixed a function argument error ... Signed-off-by: Florian Fleissner <florian.fleissner@inpartik.de>	6 years ago
Florian Fleissner	f0102dba00	Keymaps converted from 2D to 1D arrays ... New `PER_KEY_DATA` and `PER_KEY_DATA_STACKED` macros were introduced that can be used to feed keymap associated information to functions, constructors or to initialize the keymap. The user accessed macros `KEYMAP` and `KEYMAP_STACKED` are now wrappers that pass `XXX` as default value for unused keys. The new keymap array is named `keymap_linear`. The old symbol name is now used for a deprecated compatibility wrapper data structure. Signed-off-by: Florian Fleissner <florian.fleissner@inpartik.de>	6 years ago
Florian Fleissner	f764a78ecd	New classes/macros: ... * a class Bitfield that does the general bit handling. * a utility function generateBitfield that simplifies bitfield creation * function macros KEYMAP_BITFIELD and KEYMAP_BITFIELD_STACKED that enable definitions of keymap bitfields in the same way as keymaps are defined All exported functions live in namespace kaleidoscope::bitfields. Please note, that KEYMAP_BITFIELD is only defined if a keyboard hardware defines a KEYMAP_GENERIC macro and KEYMAP_BITFIELD_STACKED only if the hardware header defines KEYMAP_STACKED_GENERIC (not all keyboard hardwares define both). Expected side effects: As all symbols and macros are newly introduced, nothing is expected to break. Signed-off-by: Jesse Vincent <jesse@keyboard.io>	6 years ago