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
..
src	Update MouseMotion and CursorMoved docs (#5090)	2022-06-26 13:40:43 +00:00
Cargo.toml	Bump Bevy to 0.8.0-dev (#4505)	2022-04-17 23:04:52 +00:00