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.

Sign up for GitHub

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

Jump to bottom

Support to get gamepad button/trigger values using Axis<GamepadButton> #683

Merged
merged 1 commit into from
Oct 15, 2020
Merged

Support to get gamepad button/trigger values using Axis<GamepadButton> #683

merged 1 commit into from
Oct 15, 2020

Conversation

simpuid
Copy link
Contributor

@simpuid simpuid commented Oct 15, 2020

Fixes #680 but uses Axis<GamepadButton> instead of modifying Input struct to store floating values like #681
Updated the gamepad_input example

@Moxinilian Moxinilian added C-Feature A new feature, making something new possible A-Input Player input via keyboard, mouse, gamepad, and more labels Oct 15, 2020
@bhickey bhickey mentioned this pull request Oct 15, 2020
Closed
@cart
Copy link
Member

cart commented Oct 15, 2020

nice. looks good to me!

@cart cart merged commit dd91f8e into bevyengine:master Oct 15, 2020
joshuajbouw pushed a commit to joshuajbouw/bevy that referenced this pull request Oct 24, 2020
@simpuid @joshuajbouw
Add support to get gamepad button/trigger values using Axis<GamepadBu…
81f1f7c 
…tton> (bevyengine#683)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
A-Input Player input via keyboard, mouse, gamepad, and more C-Feature A new feature, making something new possible
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

GamepadButton does not retain trigger values
3 participants
@simpuid @cart @Moxinilian