Input

Bind physical controls to game actions, consume ordered records, and route keyboard/text focus. Bind input actions provides direct binding and reusable consumer-context sequences; Input lists the controls and public types. Use gamepad availability to subscribe to sampled connection changes and obtain an initial state.

• Bind input actions
• Actions, records, capture and focus

Use the GUI guide when a toolkit session should interpret the records. Capture requests and focus leases have separate lifetimes and neither retains a native window. Use action contexts for scoped bindings and Create a PlayerController to translate each consumer’s local actions into application commands.