Temporarily back out use of KeyAddr in one function in ATMegaKeyboard.

The "new" code we've backed out caused all key events to be about key
0,0. I suspect that this is GCC doing something crazy with that one
function.  I don't understand what's going on. @noseglasses: any idea?
pull/689/head
Jesse Vincent 5 years ago
parent 0094832b12
commit ebeb173cb8
No known key found for this signature in database
GPG Key ID: 122F5DF7108E4046

@ -110,7 +110,8 @@ void __attribute__((optimize(3))) ATMegaKeyboard::actOnMatrixScan() {
uint8_t keyState = (bitRead(KeyboardHardware.previousKeyState_[row], col) << 0) |
(bitRead(KeyboardHardware.keyState_[row], col) << 1);
if (keyState) {
handleKeyswitchEvent(Key_NoKey, KeyAddr(row, col), keyState);
//handleKeyswitchEvent(Key_NoKey, KeyAddr(row, col), keyState);
handleKeyswitchEvent(Key_NoKey, row, col, keyState);
}
}
KeyboardHardware.previousKeyState_[row] = KeyboardHardware.keyState_[row];

Loading…
Cancel
Save