area10 members
Testing & debugging
Drive input from a test: keys, clicks, touches and gamepads.
Start here
datumhue.debug.input.keyPress (down = true) or release a key, as a keyboard does: from the next frame on the input readers,input.on_keyand the focused widget see it, so every callback run in that frame sees the press or release once; the run that made the call does not.datumhue.debug.input.clickPress a mouse button at the current pointer position and release it shortly after, astapdoes a key: the press reaches the readers from the next frame on.
The functions a package's tests run with, and their matchers, are in Package testing.
In this area
- datumhue.debug.inputSynthetic keyboard, pointer, touch and gamepad input for development: injected keys, buttons, wheel turns, touches and pad input reach the input state from the next frame on, as real input arriving between frames does, and focus and every input read treat them as real input -- except the widgets that act outside the app (file-access and copy buttons, links, and a workstation dialog's buttons that open a web page or quit the workstation, such as the quit confirmation's Quit), which ignore synthetic input.