-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
GamepadEventsRaw vs GamepadEvents is confusing and undocumented #5544
Copy link
Copy link
Closed
Labels
A-InputPlayer input via keyboard, mouse, gamepad, and morePlayer input via keyboard, mouse, gamepad, and moreC-DocsAn addition or correction to our documentationAn addition or correction to our documentation
Description
What problem does this solve or what need does it fill?
When mocking gamepad input, you must send GamepadEventsRaw, or it will not be transformed into Input and Axis data correctly.
However, there are not docs to explain the difference or warn users of this footgun.
What solution would you like?
- Add documentation to
GamepadEventsandGamepadEventsRawexplaining their purpose. - Add a doc test demonstrating how to use
GamepadEventsRawto mock gamepad input.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-InputPlayer input via keyboard, mouse, gamepad, and morePlayer input via keyboard, mouse, gamepad, and moreC-DocsAn addition or correction to our documentationAn addition or correction to our documentation