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

&rgb_ug RGB_COLOR_HSB on split keyboard is not global when used within macro #1347

Open
ivandaho opened this issue Jun 16, 2022 · 2 comments · May be fixed by #1630
Open

&rgb_ug RGB_COLOR_HSB on split keyboard is not global when used within macro #1347

ivandaho opened this issue Jun 16, 2022 · 2 comments · May be fixed by #1630

Comments

@ivandaho
Copy link

When using using the example code as seen in https://zmk.dev/docs/behaviors/macros#layer-activation--more for Layer + Underglow Color, underglow color is only set for the central side of the keyboard during macro execution

  • Color for peripheral side is unaffected by the macro
  • If i change underglow color directly with &rgb_ug RGB_COLOR_HSB(86,81,85) outside of a macro, it changes for both sides as expected

Tested on main branch, built via docker method for Corne/NRFMicro
Unsure if any other &rgb_ug behavior is affected

reproducable in https://github.com/ivandaho/zmk/tree/corne-ivan, in case you have a corne/NRFMicro

  • run ./buildcorne.sh in app directory
  • flash firmware
  • turn on LEDs by holding these buttons on the central/left side down in this order
    • leftmost button on bottom row
    • rightmost button on bottom row
    • "D" key (4th button on 2nd row)
  • press either:
    • leftmost button on bottom row (central/left side)
    • middle button on bottom row (peripheral/right side)
@tokazio
Copy link

tokazio commented Jan 17, 2023

Same issue here https://github.com/tokazio/zmk-config-sofle

@caksoylar
Copy link
Contributor

Most likely related to #1494

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants