Kaleidoscope/src/LED-Off.h

#pragma once

#include "Kaleidoscope-LEDControl.h"

namespace kaleidoscope {
class LEDOff : public LEDMode {
 public:
  LEDOff(void) { }

 protected:
  void onActivate(void) final;
  void refreshAt(byte row, byte col) final;
};
}

extern kaleidoscope::LEDOff LEDOff;
Lift out the LED control & effect parts from the core This is a slightly tweaked version of LEDControl from core KeyboardioFirmware, along with the built-in LED effects. The one major change is that LED sync is now called just before the update, instead of at the end of the main loop. This, however, should not be a noticeable change. Signed-off-by: Gergely Nagy <algernon@madhouse-project.org> 8 years ago			`#pragma once`

The Big Rename Renamed the library to Kaleidoscope-LEDControl, and followed up with other renames. Signed-off-by: Gergely Nagy <algernon@madhouse-project.org> 8 years ago			`#include "Kaleidoscope-LEDControl.h"`
Lift out the LED control & effect parts from the core This is a slightly tweaked version of LEDControl from core KeyboardioFirmware, along with the built-in LED effects. The one major change is that LED sync is now called just before the update, instead of at the end of the main loop. This, however, should not be a noticeable change. Signed-off-by: Gergely Nagy <algernon@madhouse-project.org> 8 years ago
Major update of how LED modes work There were a number of issues with the model we had before, namely that plugins that changed LED colors outside of LED modes had no way to signal "go back to whatever color this key was". To this end, the `LEDMode.refreshAt` method is introduced, which these plugins can call to tell the mode to update a given key. As part of this, the API was redesigned, with code that is common between all LED modes moving to the base class, among other things, much better names, and a flow of control that is easier to follow. In the new setup, there are four methods a LED mode can implement: - `setup()` to do boot-time initialization (registering hooks, etc). - `onActivate()` called every time the mode is activated. - `update()` called each cycle. - `refreshAt()` may be called by other plugins to refresh a particular key. All of these are protected methods, to be called via `LEDControl` only. Much of the new API design was done by @cdisselkoen, huge thanks for his work! Fixes #9. Signed-off-by: Gergely Nagy <kaleidoscope@gergo.csillger.hu> 7 years ago			`namespace kaleidoscope {`
			`class LEDOff : public LEDMode {`
Lift out the LED control & effect parts from the core This is a slightly tweaked version of LEDControl from core KeyboardioFirmware, along with the built-in LED effects. The one major change is that LED sync is now called just before the update, instead of at the end of the main loop. This, however, should not be a noticeable change. Signed-off-by: Gergely Nagy <algernon@madhouse-project.org> 8 years ago			`public:`
Major update of how LED modes work There were a number of issues with the model we had before, namely that plugins that changed LED colors outside of LED modes had no way to signal "go back to whatever color this key was". To this end, the `LEDMode.refreshAt` method is introduced, which these plugins can call to tell the mode to update a given key. As part of this, the API was redesigned, with code that is common between all LED modes moving to the base class, among other things, much better names, and a flow of control that is easier to follow. In the new setup, there are four methods a LED mode can implement: - `setup()` to do boot-time initialization (registering hooks, etc). - `onActivate()` called every time the mode is activated. - `update()` called each cycle. - `refreshAt()` may be called by other plugins to refresh a particular key. All of these are protected methods, to be called via `LEDControl` only. Much of the new API design was done by @cdisselkoen, huge thanks for his work! Fixes #9. Signed-off-by: Gergely Nagy <kaleidoscope@gergo.csillger.hu> 7 years ago			`LEDOff(void) { }`
LEDOff: Always set everything to off While it was a neat optimization to only turn LEDs off at init time, that is not enough if there are other plugins in play, that work with the LEDs independently of the active LED mode. Such a plugin is LED-ActiveModColor, which never turns LEDs off, and relies on the LED mode to do that. Since LEDOff did not turn things off on update(), when used together with LED-ActiveModColor, the LEDs under the modifiers stayed active, even after the modifiers went inactive. With this simple change, LEDOff will now update, and the problem's gone. Signed-off-by: Gergely Nagy <algernon@madhouse-project.org> 8 years ago
Major update of how LED modes work There were a number of issues with the model we had before, namely that plugins that changed LED colors outside of LED modes had no way to signal "go back to whatever color this key was". To this end, the `LEDMode.refreshAt` method is introduced, which these plugins can call to tell the mode to update a given key. As part of this, the API was redesigned, with code that is common between all LED modes moving to the base class, among other things, much better names, and a flow of control that is easier to follow. In the new setup, there are four methods a LED mode can implement: - `setup()` to do boot-time initialization (registering hooks, etc). - `onActivate()` called every time the mode is activated. - `update()` called each cycle. - `refreshAt()` may be called by other plugins to refresh a particular key. All of these are protected methods, to be called via `LEDControl` only. Much of the new API design was done by @cdisselkoen, huge thanks for his work! Fixes #9. Signed-off-by: Gergely Nagy <kaleidoscope@gergo.csillger.hu> 7 years ago			`protected:`
			`void onActivate(void) final;`
			`void refreshAt(byte row, byte col) final;`
Lift out the LED control & effect parts from the core This is a slightly tweaked version of LEDControl from core KeyboardioFirmware, along with the built-in LED effects. The one major change is that LED sync is now called just before the update, instead of at the end of the main loop. This, however, should not be a noticeable change. Signed-off-by: Gergely Nagy <algernon@madhouse-project.org> 8 years ago			`};`
Major update of how LED modes work There were a number of issues with the model we had before, namely that plugins that changed LED colors outside of LED modes had no way to signal "go back to whatever color this key was". To this end, the `LEDMode.refreshAt` method is introduced, which these plugins can call to tell the mode to update a given key. As part of this, the API was redesigned, with code that is common between all LED modes moving to the base class, among other things, much better names, and a flow of control that is easier to follow. In the new setup, there are four methods a LED mode can implement: - `setup()` to do boot-time initialization (registering hooks, etc). - `onActivate()` called every time the mode is activated. - `update()` called each cycle. - `refreshAt()` may be called by other plugins to refresh a particular key. All of these are protected methods, to be called via `LEDControl` only. Much of the new API design was done by @cdisselkoen, huge thanks for his work! Fixes #9. Signed-off-by: Gergely Nagy <kaleidoscope@gergo.csillger.hu> 7 years ago			`}`
Lift out the LED control & effect parts from the core This is a slightly tweaked version of LEDControl from core KeyboardioFirmware, along with the built-in LED effects. The one major change is that LED sync is now called just before the update, instead of at the end of the main loop. This, however, should not be a noticeable change. Signed-off-by: Gergely Nagy <algernon@madhouse-project.org> 8 years ago
Major update of how LED modes work There were a number of issues with the model we had before, namely that plugins that changed LED colors outside of LED modes had no way to signal "go back to whatever color this key was". To this end, the `LEDMode.refreshAt` method is introduced, which these plugins can call to tell the mode to update a given key. As part of this, the API was redesigned, with code that is common between all LED modes moving to the base class, among other things, much better names, and a flow of control that is easier to follow. In the new setup, there are four methods a LED mode can implement: - `setup()` to do boot-time initialization (registering hooks, etc). - `onActivate()` called every time the mode is activated. - `update()` called each cycle. - `refreshAt()` may be called by other plugins to refresh a particular key. All of these are protected methods, to be called via `LEDControl` only. Much of the new API design was done by @cdisselkoen, huge thanks for his work! Fixes #9. Signed-off-by: Gergely Nagy <kaleidoscope@gergo.csillger.hu> 7 years ago			`extern kaleidoscope::LEDOff LEDOff;`