datumhue.debug.input

Press (down = true) or release a key, as a keyboard does: from the next frame on the input readers, input.on_key and 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. The key stays held until released. Pressing a held key or releasing one that is up does nothing. A side-agnostic modifier name presses its left key.

Press a key and release it shortly after: one clean press-release to every consumer, the press from the next frame on, as key delivers it. A side-agnostic modifier name taps its left key.

Move the pointer to a position in UI px from the top-left of the calling app's content area, the frame input.app_mouse_position and UiElement.bounds use, so bounds.center points at the element at every zoom and stretch mode. While the caller's content area is not laid out (always, in a service app), from the top-left of the bootstrap's.

Press a mouse button at the current pointer position and release it shortly after, as tap does a key: the press reaches the readers from the next frame on. Defaults to the left button.

Set a touch point's state at a position in UI px from the top-left of the calling app's content area, the frame cursor takes: down = true starts the touch with this id, or moves it when already down; down = false ends it (a no-op when not down). The input readers see it from the next frame on, as they see a real touch.

Press (down = true) or release a mouse button at the current pointer position, reaching the readers from the next frame on, as key does. The button stays held until released, so cursor moves in between drag it, as a real mouse does. Pressing a held button or releasing one that is up does nothing.

Turn the mouse wheel once at the current pointer position: one wheel event, which the scroll containers under the pointer take. input.scroll_delta reads it in the device's units, as it reads a real one: lines, or for pixel physical px, the UI px times the scale factor screen.resolution reports and screen.zoom. Positive dy is the wheel turned away from the user, which scrolls toward the top; positive dx scrolls toward the left. unit defaults to lines. Raises for a delta that is not a finite number.

Press (down = true) or release a button on the debug pad, a virtual gamepad the first pad call connects, named "debug pad". From the next frame on, the gamepad readers, input.last_source, focus navigation and window-manager grabs see it as a connected pad, listed by input.gamepads. The button stays as set until a later call changes it. The debug pad has no motors, so input.rumble on it does nothing. pad_id picks a debug pad by the id input.gamepads reports; without it, the first debug pad. Raises when pad_id is not a debug pad.

Set a stick on the debug pad (connecting it, as debug.input.gamepad does) to a position with each axis within -1..1, y up: the vector input.stick reads from the next frame on. The stick stays there until a later call moves it. pad_id picks the debug pad as debug.input.gamepad does. Raises for an axis outside -1..1.

Set an analog trigger on the debug pad (connecting it, as debug.input.gamepad does) to a travel within 0..1: the value input.trigger reads from the next frame on. The trigger stays there until a later call moves it. pad_id picks the debug pad as debug.input.gamepad does. Raises for a value outside 0..1.