-
-
Notifications
You must be signed in to change notification settings - Fork 39.6k
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
BT LEDs are no longer hard coded #18934
Conversation
…key they are mapped to
case KC_AP2_BT1: | ||
annepro2_ble_broadcast(0); | ||
/* FIXME: This hardcodes col/row position */ | ||
ap2_led_blink(0, 1, blue, 8, 50); | ||
ap2_led_blink(record->event.key.row, record->event.key.col, blue, 8, 50); | ||
return false; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that if someone decides to put KC_AP2_BT1
on a combo, record->event.key
will contain {KEYLOC_COMBO, KEYLOC_COMBO}
({254, 254}
) instead of real row and column numbers. If the LED firmware won't handle such out of range values correctly, you should add range checks somewhere.
And the FIXME can probably be removed too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know too much about the way combo keys work, I will look into that when I can. Thanks
Description
The keyboard BT LEDs are no longer hard coded into the keyboard but will move according to the corresponding mapping of BT Key
Types of Changes
Issues Fixed or Closed by This PR
Checklist