Closed phil-opp closed 5 years ago
Seems like I broke some tests. I will look into it…
Ok, seems like changing the state machine for scancode set 2 was the problem. I updated the PR to only apply the fixes for scancode set 1.
Thanks for finding that issue!
@thejpster Thanks! Could you release a new crates.io version with these fixes?
Sure. Am I bumping x or y in 0.x.y?
I consider this PR a bugfix, so I would probably bump the y
. But I'm also fine with bumping the x
.
Done
Thanks!
This PR updates the scancode set 1 state machine to make the
Release
andExtendedRelease
states equivalent to theStart
state. Before, aclear
call was required after each KeyEvent, because theRelease
andExtendedRelease
state were forever looping.It also fixes a bug in the new scancode 1 implementation where a decimal
80
was subtracted instead of a hexadecimal0x80
. This fixes the issue that the KeyUp event of the shift key was not recognized so that the input stayed uppercase forever.This PR also removes some trailing whitespace and runs rustfmt. This is of course optional and I can remove it if it's not wanted.
cc @ZerothLaw