bevy/crates/bevy_input/src
Federico Rinaldi 056f12236e Update MouseMotion and CursorMoved docs (#5090)
# Objective

- Fixes #5083 

## Solution

I looked at the implementation of those events. I noticed that they both are adaptations of `winit`'s `DeviceEvent`/`WindowEvent` enum variants. Therefore I based the description of the items on the documentation provided by the upstream crate. I also added a link to `CursorMoved`, just like `MouseMotion` already has.

## Observations

- Looking at the implementation of `MouseMotion`, I noticed the `DeviceId` field of the `winit` event is discarded by `bevy_input`. This means that in the case a machine has multiple pointing devices, it is impossible to distinguish to which one the event is referring to. **EDIT:** just tested, `MouseMotion` events are emitted for movement of both mice.
2022-06-26 13:40:43 +00:00
..
axis.rs Change gamepad.rs tuples to normal structs (#4519) 2022-05-02 13:20:55 +00:00
gamepad.rs Change gamepad.rs tuples to normal structs (#4519) 2022-05-02 13:20:55 +00:00
input.rs Add Input::reset_all (#5015) 2022-06-20 18:31:46 +00:00
keyboard.rs Update keyboard.rs docs in bevy_input (#4517) 2022-05-17 04:16:54 +00:00
lib.rs Allow closing windows at runtime (#3575) 2022-05-05 13:35:43 +00:00
mouse.rs Update MouseMotion and CursorMoved docs (#5090) 2022-06-26 13:40:43 +00:00
touch.rs Fixed bevy_ui touch input (#4099) 2022-06-20 20:32:19 +00:00