Report mouse motion before click

[chrisduerr]

This fixes an issue on macOS where a mouse click would be generated,
without ever getting a mouse motion to the position before the click.
This leads to the application thinking the mouse click occurred at a
position other than the actual mouse location.

This happens due to mouse motion above the window not automatically
giving focus to the window, unless it is actually clicked, making it
possible to move the window without motion events.

Fixes #942.

[SergeevPavel]

Could we also trigger mouse motion before mouse wheel event?

[chrisduerr]

I've added it for pressure change and scroll too, since that makes some sense.

[chrisduerr]

Test failure on Windows should be unrelated to this macOS PR.

[ryanisaacg]

I merged master into this branch which should solve the CI conflicts and get this ready for a merge.

[QuentinPerez]

I have the same issue thank you for the patch, I was wondering if we could add x and y in the mouseClick event instead of doing magic like saving the last x,y sent by the last Mouse::CursorMoved ?

[ryanisaacg]

@QuentinPerez Do you mean in the external Winit API?

[QuentinPerez]

Yes, like

winit/src/event.rs

Line 256 in 849b8f5

position: PhysicalPosition<f64>,

but for

winit/src/event.rs

Line 277 in 849b8f5

MouseInput {

don't know if it's the best way to do things.

I'm using iced and I would like to draw a point when I click on the canvas but for that, I need to store the last position received by CursorMoved to know where I can draw on the MouseInput event.

[ryanisaacg]

@QuentinPerez That discussion is probably best for a meta-issue on the tracker, like this previous issue.. This PR is fixing an internal bug regarding emitting the CursorMoved on macOS, specifically.