IOKit HID Input
Stable input uses NSEvent, not raw IOKit HID events.
Availability
The advertised workflow is not available as a connected feature in stable v0.5.1. Source components or future work do not make it a shipped capability.
Reviewed against stable v0.5.1. Rust candidate additions are labeled separately. Release status.
The pain this solves
- Input-latency claims depend on the actual event path.
- Raw HID input should not be implied when the app uses standard app events.
What ships with it
- Stable terminal input uses NSEvent-based handling.
- The performance README notes removal of the former LowLatencyInput reference.
- No IOKit HID terminal-input route was found.
Questions this answers
- Does stable terminal input use IOKit HID?
- What input event path does the stable terminal view use?
How it works
The stable terminal view handles keyboard events through NSEvent-based input code, including its key-down and keyboard-input policy path.
The app also uses NSEvent monitors for relevant event handling. The performance README notes that an earlier LowLatencyInput file reference was removed.
No stable IOKit HID capture path or raw HID-to-terminal pipeline was found. The website should not imply that Chau7 bypasses NSEvent or receives universal raw keyboard events.
Why it matters
Input architecture affects what a terminal can observe and how events are delivered. Chau7's stable source supports an NSEvent-based description, not an IOKit low-latency pipeline.
Frequently asked questions
Does stable Chau7 use IOKit HID for terminal keystrokes?
No IOKit HID terminal-input path was found in the stable source audit.
What input path is present?
The stable terminal view handles input through NSEvent-based event handling.