Skip to content
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

Adjust the Model100 firmware to default to Colormap #26

Open
algernon opened this issue Sep 25, 2022 · 4 comments
Open

Adjust the Model100 firmware to default to Colormap #26

algernon opened this issue Sep 25, 2022 · 4 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@algernon
Copy link
Contributor

It looks like the way we handle LED effects is a frequent source of confusion: people set up colors with Chrysalis, and then wonder why they don't show up. While Chrysalis could do a better job at explaining that they need to switch to the Colormap effect, it would be even better if the keyboard helped them in that regard, too.

What if we defaulted to Colormap, if there is no default LED mode set?

I wouldn't move the plugin in the plugin list, but do something like: if (DefaultLEDModeConfig.isUninitialized()) ColormapEffect.activate();.

Since the palette is all black by default, this would mean that the keyboard behaves the same out of the box as with LEDOff: all LEDs are off. But once a palette & colormap is saved, they'd be active immediately, without having to explicitly switch the mode.

@algernon algernon added bug Something isn't working enhancement New feature or request labels Sep 25, 2022
@algernon
Copy link
Contributor Author

Actually, the Model100 firmware already has:

  // Unless configured otherwise with Chrysalis, we want to make sure that the
  // firmware starts with LED effects off. This avoids over-taxing devices that
  // don't have a lot of power to share with USB devices
  DefaultLEDModeConfig.activateLEDModeIfUnconfigured(&LEDOff);

We could adjust that to use &ColormapEffect, along with the comment above it.

@obra
Copy link
Member

obra commented Sep 25, 2022

So the reason we default to all-off is that otherwise it draws more power than apple's mobile devices accept and gets force-disconnected immediately.

Instead of doing this in firmware, I wonder if we want to do this with Chrysalis the first time an update that enables colors on the colormap is made.

@algernon
Copy link
Contributor Author

That's not a bad idea. We'll need to make things a bit smarter first, to figure out the index of the colormap plugin, to be able to properly set it as the default from Chrysalis. But I like the idea, lets do this on the Chrysalis side.

(Not closing this yet, will do so once I open an issue on the Chrysalis side)

@fredcallaway
Copy link

Bump. This confusion just got me. Is there a hot fix in the mean time? I thought I would find a default LED mode in the Chrysalis settings because DefaultLEDModeConfig is included in the current firmware (0.91). Am I missing something obvious?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants