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

fix: layer_state_set_user didn't trigger if VOYAGER_USER_LEDS was defined #396

Merged
merged 1 commit into from
Aug 5, 2024

Conversation

Ofenhed
Copy link

@Ofenhed Ofenhed commented Aug 2, 2024

No description provided.

Copy link
Collaborator

@fdidron fdidron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks !

@fdidron fdidron merged commit cc1d6fd into zsa:firmware24 Aug 5, 2024
4 checks passed
@Ofenhed Ofenhed deleted the firmware24 branch November 10, 2024 14:11
marienz added a commit to marienz/qmk_firmware that referenced this pull request Dec 7, 2024
Before commit b46f5e2,
layer_state_set_kb was only defined if MOONLANDER_USER_LEDS was not set.
With MOONLANDER_USER_LEDS set, the default layer_state_set_kb provided
by QMK takes care of calling layer_state_set_user.

After that commit, layer_state_set_kb is defined unconditionally, but
most of its body is still ifdef'd out if MOONLANDER_USER_LEDS is set.
That includes layer_state_set_user, which looks like an oversight.

Run layer_state_set_user unconditionally.

This is the same fix as zsa#396 for voyager. It looks like the other ZSA
keyboards do not have the same problem.

Alternatively, we could go back to the old approach of defining the
function conditionally, but this makes it a little harder to reintroduce
the same problem.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants