140d9612e6
# Objective Add `GamepadButtonInput` event Resolves #8988 ## Solution - Add `GamepadButtonInput` type - Emit `GamepadButtonInput` events whenever `Input<GamepadButton>` is written to - Update example --------- Co-authored-by: François <mockersf@gmail.com>
64 lines
2.5 KiB
Rust
64 lines
2.5 KiB
Rust
//! Iterates and prints gamepad input and connection events.
|
|
|
|
use bevy::{
|
|
input::gamepad::{
|
|
GamepadAxisChangedEvent, GamepadButtonChangedEvent, GamepadButtonInput,
|
|
GamepadConnectionEvent, GamepadEvent,
|
|
},
|
|
prelude::*,
|
|
};
|
|
|
|
fn main() {
|
|
App::new()
|
|
.add_plugins(DefaultPlugins)
|
|
.add_systems(Update, (gamepad_events, gamepad_ordered_events))
|
|
.run();
|
|
}
|
|
|
|
fn gamepad_events(
|
|
mut connection_events: EventReader<GamepadConnectionEvent>,
|
|
mut axis_changed_events: EventReader<GamepadAxisChangedEvent>,
|
|
// Handles the continuous measure of how far a button has been pressed down, as measured
|
|
// by `Axis<GamepadButton>`. Whenever that value changes, this event is emitted.
|
|
mut button_changed_events: EventReader<GamepadButtonChangedEvent>,
|
|
// Handles the boolean measure of whether a button is considered pressed or unpressed, as
|
|
// defined by the thresholds in `GamepadSettings::button_settings` and measured by
|
|
// `Input<GamepadButton>`. When the threshold is crossed and the button state changes,
|
|
// this event is emmitted.
|
|
mut button_input_events: EventReader<GamepadButtonInput>,
|
|
) {
|
|
for connection_event in connection_events.iter() {
|
|
info!("{:?}", connection_event);
|
|
}
|
|
for axis_changed_event in axis_changed_events.iter() {
|
|
info!(
|
|
"{:?} of {:?} is changed to {}",
|
|
axis_changed_event.axis_type, axis_changed_event.gamepad, axis_changed_event.value
|
|
);
|
|
}
|
|
for button_changed_event in button_changed_events.iter() {
|
|
info!(
|
|
"{:?} of {:?} is changed to {}",
|
|
button_changed_event.button_type,
|
|
button_changed_event.gamepad,
|
|
button_changed_event.value
|
|
);
|
|
}
|
|
for button_input_event in button_input_events.iter() {
|
|
info!("{:?}", button_input_event);
|
|
}
|
|
}
|
|
|
|
// If you require in-frame relative event ordering, you can also read the `Gamepad` event
|
|
// stream directly. For standard use-cases, reading the events individually or using the
|
|
// `Input<T>` or `Axis<T>` resources is preferable.
|
|
fn gamepad_ordered_events(mut gamepad_events: EventReader<GamepadEvent>) {
|
|
for gamepad_event in gamepad_events.iter() {
|
|
match gamepad_event {
|
|
GamepadEvent::Connection(connection_event) => info!("{:?}", connection_event),
|
|
GamepadEvent::Button(button_event) => info!("{:?}", button_event),
|
|
GamepadEvent::Axis(axis_event) => info!("{:?}", axis_event),
|
|
}
|
|
}
|
|
}
|