Can't change colors on layer 1

[darinclarkdev]

Chrysalis will pretend it works but as you can see it doesn't.

[obra]

I believe that what you're running into isn't "the right half" so much as "the numpad layer's numpad keys". Is that right? ᐧ

On Fri, Oct 4, 2019 at 10:04 AM Darin Clark [email protected] wrote:

Chrysalis will pretend it works but as you can see it doesn't. The left half will accept color changes and some blank keys on the right half. The left half also doesn't accept key mappings in layer 1. [image: 20191003_145657] https://user-images.githubusercontent.com/29046432/66225490-29adfb80-e69e-11e9-97b8-8c0e61ac6b53.jpg

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/keyboardio/Chrysalis/issues/430?email_source=notifications&email_token=AAALC2EOV2KTTEDDE6CZMT3QM5ZS7A5CNFSM4I5SHE52YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HPXJSEA, or mute the thread https://github.com/notifications/unsubscribe-auth/AAALC2HDYGZ7RVWDHPACCMLQM5ZS7ANCNFSM4I5SHE5Q .

[darinclarkdev]

It is any key on layer 1. If you happen to be locked on layer one when you save changes some of the colors will temporarily work. As soon as you switch to layer 0 and back to layer 1 they are all red again.

[sonicbhoc]

I have the same problem. but I can't even get it to temporarily work on mine.

[tmarzolf]

I ran into something similar on Layer 1 - red keys that I couldn't change the color. I ended up abandoning Layer 1...

[algernon]

This is, indeed, the Numpad plugin overriding custom colors. We'll need to figure something out about that.

[algernon]

In the not too distant future, we'll be updating the firmware so that it ships with a built-in colormap that renders the separate Numpad plugin obsolete. Once that happens, this issue will stop being a problem.