The code for guarding against integer overflow on the prior interval timestamp was in the wrong place, and wouldn't get executed on cycles when the keyboard was idle, leading to a very slim chance of getting the wrong qukey value if all keys were idle long enough (65 seconds). Also fixed the same problem in the first quarter-second after the keyboard power on. Not likely to ever be observed, but costs nothing extra to fix. Signed-off-by: Michael Richters <gedankenexperimenter@gmail.com>pull/971/head
parent
9e1aaac3d8
commit
0d788bb718
Loading…
Reference in new issue