Problem Statement
Currently handleKeyPress accepts a raw evdev keycode (UInt16 key). This has two problems:
- Clients must know evdev keycodes — not portable across keyboard hardware or layouts.
- No layout negotiation — when a test replays a recording on a device with a different keyboard layout, key semantics are wrong.
Problem Statement
Currently
handleKeyPressaccepts a raw evdev keycode (UInt16 key). This has two problems: