Instead of guarding the ATMegaKeyboard files with an `#if` that hard-coded which keyboards are based on the class, guard them with `KALEIDOSCOPE_WITH_ATMEGA_KEYBOARD`, set by the main hardware headers. Those headers get included early, and are as such, a perfect way to guard these things. This way if we add a new keyboard using the base class, we don't have to modify the base class itself, and the new hardware plugin can be entirely self-contained. Signed-off-by: Gergely Nagy <algernon@keyboard.io>pull/464/head
parent
6d41c79a5b
commit
1d65c02f9f
Loading…
Reference in new issue