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

[Keymap] layer indicator lights #10004

Merged
merged 2 commits into from
Aug 17, 2020
Merged

Conversation

stanrc85
Copy link
Contributor

Making better use of num lock and scroll lock indicators lights by using them for layer indicators instead.

Description

Types of Changes

  • Core
  • Bugfix
  • New feature
  • Enhancement/optimization
  • Keyboard (addition or update)
  • Keymap/layout/userspace (addition or update)
  • Documentation

Issues Fixed or Closed by This PR

Checklist

  • My code follows the code style of this project: C, Python
  • I have read the PR Checklist document and have made the appropriate changes.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • I have tested the changes and verified that they work and don't break anything (as well as I can manage).

@fauxpark fauxpark requested a review from a team August 12, 2020 13:44
@noroadsleft noroadsleft merged commit 2ddcd81 into qmk:master Aug 17, 2020
@noroadsleft
Copy link
Member

Thanks!

@stanrc85 stanrc85 deleted the feature/update branch August 17, 2020 09:09
nicocesar pushed a commit to nicocesar/qmk_firmware that referenced this pull request Sep 6, 2020
* move caps lock indicator position

* use num lock and scroll lock as layer indicators
BorisTestov pushed a commit to BorisTestov/qmk_firmware that referenced this pull request May 23, 2024
* move caps lock indicator position

* use num lock and scroll lock as layer indicators
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.

3 participants