Skip to content

GamepadEventsRaw vs GamepadEvents is confusing and undocumented #5544

@alice-i-cecile

Description

@alice-i-cecile

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?

  1. Add documentation to GamepadEvents and GamepadEventsRaw explaining their purpose.
  2. Add a doc test demonstrating how to use GamepadEventsRaw to mock gamepad input.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-InputPlayer input via keyboard, mouse, gamepad, and moreC-DocsAn addition or correction to our documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions