scrcpy reporting hover events with tool type mouse, but click with tool type finger

[gmackall]

Hi, I have a question about how scrcpy delivers MotionEvents
https://github.com/Genymobile/scrcpy/blob/c5ed2cfc28ee7c7b59b11eb4db1258ac1c633bff/server/src/main/java/com/genymobile/scrcpy/control/Controller.java#L408C68-L408C83

scrcpy/server/src/main/java/com/genymobile/scrcpy/control/Controller.java

Line 413 in c5ed2cf

pointerProperties[pointerIndex].toolType = MotionEvent.TOOL_TYPE_FINGER;

In particular, why does scrcpy deliver mouse clicks as originating from a TOOL_TYPE_FINGER, (or more generally MotionEvents that are not of type MotionEvent.ACTION_HOVER_MOVE, and therefore continue to the else case)? Is this intentional?

My motivation for asking is that I'm wondering how Flutter should handle these inputs from scrcpy, as it is currently the source of a bug (flutter/flutter#160144)

[rom1v]

In particular, why does scrcpy deliver mouse clicks as originating from a TOOL_TYPE_FINGER, (or more generally MotionEvents that are not of type MotionEvent.ACTION_HOVER_MOVE, and therefore continue to the else case)? Is this intentional?

Yes. The root cause is that when the user uses the computer mouse, we really want to inject events as if they originated from a finger, not a mouse, because the behavior is different. For example, the selection vs scroll is different with a mouse and a finger. And in some games, the mouse just does not work.

But at the same time, secondary clicks (right or middle click) and hover, which require a mouse type, must still work. So there is no perfect solution.

More details in these commits:

• c7b1d0e
• 6808288
• 773c23f
• 51fee79