-
-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Fixes for encoder abstraction. #23195
Conversation
066d916
to
1d716ae
Compare
1d716ae
to
50bb700
Compare
As mentioned in Discord, this didn't help. I might poke around bit myself, but not sure if I'll get anywhere. But happy test anything. Just @ me or I'll keep an eye on this pull request. |
This seems to help. In the worst-case scenario of a loaded-up keymap/userspace and a pointing device on the slave, I could not observe a spurious encoder event within 30 minutes, when it occured at least once within one minute before in this scenario. |
This is working for me so far, the second encoder is now usable. |
I can also confirm it's working - Sofle RGB here |
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.
Notes for self
Still fine on my end, encoders on both sides of Sofle RGB working correctly. Thank You @tzarc. <3
|
Sorry for the delay! I can also confirm that it's still fine as of 5bf5fc1: I can no longer provoke encoder misbehaviour. |
Description
As reported on Discord (here onwards), and subsequently #23191.
Types of Changes
Issues Fixed or Closed by This PR
Checklist