-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Model01 experimental firmware has NumPad LED effect active #4
Comments
This will be a tough one. In theory, all we need is a way to disable the Numpad plugin. In practice, we need to figure out when to do that. |
If you’re using chrysalis to edit your color maps do you ever want NumPad enabled? Or another possibility is to put a flag in the EPROM for which layer to use with NumPad and make it possible for it to be whatever you want. |
If colormap is used, then numpad should be off, indeed. It's... not easy to do that without introducing a dependency on Numpad to Colormap, which I'd rather avoid. Unless - as you wrote - we write a byte to eeprom and use that to toggle Numpad off. Alternatively, I could remove the Numpad plugin from the experimental firmware, under the assumption that people using the experimental firmware will want to use Colormap anyway. (We should probably figure out what the goal of the experimental firmware are, and how much it can deviate from the default, but that's another topic...) |
That’s actually what I was getting at, sorry I wasn’t clear. :) |
I will not be touching the Model01 firmware, but for the Model 100 firmware, we're in the process of phasing out the NumPad plugin in favour of Colormap + a suitable default palette & map. |
When switching to layer 1 while using the experimental firmware, the NumPad LED effect still activates, overriding whatever color scheme is configured in Chrysalis.
The text was updated successfully, but these errors were encountered: