Sending window events via the ECS doesn't update the corresponding fields on the Window.

[alice-i-cecile]

Bevy version

0.8.1

What you did

Sent a CursorMoved event, or another event from bevy_window.

What went wrong

The corresponding fields on the appropriate Window were not updated.

Additional information

This was discovered while attempting to get input playback working properly: Leafwing-Studios/leafwing_input_playback#10

Users can workaround this by manually setting the appropriate fields: https://docs.rs/bevy/latest/bevy/window/struct.Window.html#method.set_cursor_position. While it would be nice to have #4530 to make this pattern easier, simply adding a set of systems that runs at the start of each frame, reads these events and then sets the corresponding window fields would probably be enough to fix this surprising behavior.

[mockersf]

This is expected, events like CursorMoved are emitted by the window when it changes, not consumed by it.

Trying to use the mouse position both from events and from the window resource at the same time can never be trusted as the window resource will only show the state as of the latest event from winit. Any intermediate event won't have the same value.

[DJMcNab]

To clarify, the correct way do this is to make your own custom runner which both updates the window fields and sends the events you need. That is, mock bevy_winit

[alice-i-cecile]

Alright, I've managed to get this working without upstream changes. #4537 will make the strategy proposed by @DJMcNab much less painful.