Commit graph

7 commits

Author SHA1 Message Date
8a0760a620
chore: clippy concurrency (#10)
All checks were successful
Publish nightly release / build (push) Successful in 1m36s
Reviewed-on: #10
2024-04-08 21:25:02 +00:00
702cbe5eb0
add mode to further improve input latency while maintaining accuracy (#8)
All checks were successful
Publish nightly release / build (push) Successful in 1m16s
This feels even hackier than consistency mode... we hold off on writing USB reports until the button state actually changes. Passes the input integrity benchmark with ~99.6%, but that doesn't mean much since the challenge is preserving input integrity for inputs less than 8.33ms apart.

Current rate limiter looks good from initial measurements, so will probably merge this at some point and leave it up to users to try the mode out or not. For now, I'd still recommend regular consistency mode, it's still hacky, but way less than this.

Also, not breaking because the new enum for input consistency mode is backward compatible with the bool.

Reviewed-on: #8
2024-04-08 20:53:23 +00:00
c2e4066125
chore: cancel previous clippy runs if need be
All checks were successful
Publish nightly release / build (push) Successful in 1m38s
2024-04-08 22:40:38 +02:00
f4de1326a5
change(project): use https for git resolution
All checks were successful
Publish nightly release / build (push) Successful in 5m24s
2024-04-05 12:39:39 +02:00
5cabeeb109
fix(ci): scan host key in clippy flow
Some checks failed
Publish nightly release / build (push) Failing after 59s
2024-04-05 12:37:12 +02:00
bb2184fa29
chore(ci): use public binary cache
Some checks failed
Publish nightly release / build (push) Failing after 1m0s
2024-04-05 12:14:22 +02:00
2f49357029
chore: refactor according to clippy & clean up config (#6)
All checks were successful
Publish nightly release / build (push) Successful in 2m9s
Reviewed-on: #6
2024-04-03 16:53:52 +00:00