-
Notifications
You must be signed in to change notification settings - Fork 259
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
ColormapOverlay overlays don't seem to apply to transparent keys #1425
Comments
I don't believe that was intentional. This plugin is one of my first contributions, so I may have simply overlooked something. Will have a look this weekend |
I don't do anything in particular to prevent the led from being set if the key isn't assigned. Basically, if an overlay is defined for the given key address on that layer, Kaleidoscope/plugins/Kaleidoscope-Colormap-Overlay/src/kaleidoscope/plugin/Colormap-Overlay.cpp Lines 61 to 67 in 2c280dd
I think the error I made is that I used Layer.lookupActiveLayer rather than Layer.mostRecent to find the current layer.Kaleidoscope/plugins/Kaleidoscope-Colormap-Overlay/src/kaleidoscope/plugin/Colormap-Overlay.cpp Lines 37 to 51 in 2c280dd
Does that make sense to you? |
Now I realize that this behavior may have been intentional, even it if is counterintuitive... My use-case for the overlay plugin is to highlight my layer switches. The way it's currently set up supports lighting up keys in lower layers, provided that higher layers don't have a key assigned (i.e. transparent). I suppose it should be easy enough to add additional logic to check for an assigned color overlay at the top-most layer before falling through to lower layers. I could also add a toggle to enable/disable the option to check for overlays on lower layers. |
I was a little surprised, when testing out the replacement for the Numpad plugin, that setting an overlay on a key that didn't have anything defined on the numpad layer...just didn't light up the key. I'd expect that if I've explicitly defined an overlay, it wouldn't skip lighting up just because there was a transparent key on the keymap.
@EvyBongers - is this an intentional design? I'd love to understand the design intent better.
The text was updated successfully, but these errors were encountered: