7a29c707bf
# Objective - The `Gamepad` type is a tiny value-containing type that implements `Copy`. - By convention, references to `Copy` types should be avoided, as they can introduce overhead and muddle the semantics of what's going on. - This allows us to reduce boilerplate reference manipulation and lifetimes in user facing code. ## Solution - Make assorted methods on `Gamepads` take / return a raw `Gamepad`, rather than `&Gamepad`. ## Migration Guide - `Gamepads::iter` now returns an iterator of `Gamepad`. rather than an iterator of `&Gamepad`. - `Gamepads::contains` now accepts a `Gamepad`, rather than a `&Gamepad`.
44 lines
1.3 KiB
Rust
44 lines
1.3 KiB
Rust
//! Shows handling of gamepad input, connections, and disconnections.
|
|
|
|
use bevy::{input::gamepad::GamepadButton, prelude::*};
|
|
|
|
fn main() {
|
|
App::new()
|
|
.add_plugins(DefaultPlugins)
|
|
.add_system(gamepad_system)
|
|
.run();
|
|
}
|
|
|
|
fn gamepad_system(
|
|
gamepads: Res<Gamepads>,
|
|
button_inputs: Res<Input<GamepadButton>>,
|
|
button_axes: Res<Axis<GamepadButton>>,
|
|
axes: Res<Axis<GamepadAxis>>,
|
|
) {
|
|
for gamepad in gamepads.iter() {
|
|
if button_inputs.just_pressed(GamepadButton::new(gamepad, GamepadButtonType::South)) {
|
|
info!("{:?} just pressed South", gamepad);
|
|
} else if button_inputs.just_released(GamepadButton::new(gamepad, GamepadButtonType::South))
|
|
{
|
|
info!("{:?} just released South", gamepad);
|
|
}
|
|
|
|
let right_trigger = button_axes
|
|
.get(GamepadButton::new(
|
|
gamepad,
|
|
GamepadButtonType::RightTrigger2,
|
|
))
|
|
.unwrap();
|
|
if right_trigger.abs() > 0.01 {
|
|
info!("{:?} RightTrigger2 value is {}", gamepad, right_trigger);
|
|
}
|
|
|
|
let left_stick_x = axes
|
|
.get(GamepadAxis::new(gamepad, GamepadAxisType::LeftStickX))
|
|
.unwrap();
|
|
if left_stick_x.abs() > 0.01 {
|
|
info!("{:?} LeftStickX value is {}", gamepad, left_stick_x);
|
|
}
|
|
}
|
|
}
|