Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gamepad support #119

Closed
FaultyRAM opened this issue Jan 24, 2017 · 2 comments
Closed

Gamepad support #119

FaultyRAM opened this issue Jan 24, 2017 · 2 comments
Labels
F - wontfix This will not be worked on S - api Design and usability S - enhancement Wouldn't this be the coolest?

Comments

@FaultyRAM
Copy link

Surprised nobody's tackled this one yet. We already handle keyboard and mouse input, so gamepad input seems to be the logical next step.

Anyone looking for inspiration might want to see how SDL2 does this: basically they maintain a list of controllers and map them as closely to the XInput layout as possible. That doesn't have to be the strategy we use here, and there is some legacy code in there as well (mainly deprecated Windows APIs like DirectInput), but I think it's a reasonable starting point.

@tomaka
Copy link
Contributor

tomaka commented Jan 24, 2017

There was already a discussion here: rust-windowing/glutin#151

Basically it's "won't fix, should be an external library".

@Osspial
Copy link
Contributor

Osspial commented Apr 24, 2019

Closing in favor of #804. This is something we want, but we need help implementing it on other platforms.

@Osspial Osspial closed this as completed Apr 24, 2019
madsmtm pushed a commit to madsmtm/winit that referenced this issue Jun 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
F - wontfix This will not be worked on S - api Design and usability S - enhancement Wouldn't this be the coolest?
Development

No branches or pull requests

4 participants