Skip to content

Heatmap incorrect matrix effect workaround #16315

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

Merged
merged 2 commits into from
Apr 16, 2022

Conversation

filterpaper
Copy link
Contributor

@filterpaper filterpaper commented Feb 11, 2022

Description

This is a simple override to limit heatmap effect to pressed keys. It is a stop gap workaround of incorrect columns and rows lighting for non-rectangle key matrix. (And reformatted both paragraphs in the heatmap section)

Types of Changes

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

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).

@filterpaper filterpaper changed the base branch from master to develop February 11, 2022 23:24
@drashna drashna requested a review from a team March 8, 2022 17:01
@drashna drashna merged commit e5918cf into qmk:develop Apr 16, 2022
@drashna
Copy link
Member

drashna commented Apr 16, 2022

Thanks!

@filterpaper filterpaper deleted the heatmap-stopgap branch April 16, 2022 22:24
0xcharly pushed a commit to Bastardkb/bastardkb-qmk that referenced this pull request Jul 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants