button-pressed event too generic, split off a "key-pressed" event?
We might want to turn off the keypress haptic feedback, but not suppress generic button-presses (what would that be, like dialog box buttons, for instancee, I guess).
So would it make sense to split off a "key-pressed" event, to be able to control keyboard haptic feedback? Or is that something that the keyboard should be controlling/suppressing from the app side of things?