-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Touchscreen not captured properly without --no-mouse-hover #5067
Comments
Please run with |
Here is the log: I alternated between touch and mouse. |
Thank you. Out of curiosity, does it work with |
Yes, it does seem to work with that flag. |
OK 👌 I will probably rework the decision to inject mouse or finger. Refs #5055 (comment) |
The tool type (MOUSE or FINGER) to use depended on whether a secondary click was possible via mouse bindings. As a first step, always use a mouse tool type to break this dependency. Note that this change might cause regressions in some (unknown) cases (refs f70359f), but hopefully not. Further commits will restore a finger tool type in some specific use cases, but independent of secondary clicks. Refs #5055 <#5055> Refs #5067 <#5067>
The device source (MOUSE or FINGER) to use depended on whether a secondary click was possible via mouse bindings. As a first step, always use a mouse source to break this dependency. Note that this change might cause regressions in some (unknown) cases (refs f70359f), but hopefully not. Further commits will restore a finger source in some specific use cases, but independent of secondary clicks. Refs #5055 <#5055> Refs #5067 <#5067>
Fixed by #5076. Please test and confirm that it works 😉 |
Yes, this seems to work. Thank you! |
The device source (MOUSE or FINGER) to use depended on whether a secondary click was possible via mouse bindings. As a first step, always use a mouse source to break this dependency. Note that this change might cause regressions in some (unknown) cases (refs f70359f), but hopefully not. Further commits will restore a finger source in some specific use cases, but independent of secondary clicks. Refs Genymobile#5055 <Genymobile#5055> Fixes Genymobile#5067 <Genymobile#5067> PR Genymobile#5076 <Genymobile#5076>
The device source (MOUSE or FINGER) to use depended on whether a secondary click was possible via mouse bindings. As a first step, always use a mouse source to break this dependency. Note that this change might cause regressions in some (unknown) cases (refs f70359f), but hopefully not. Further commits will restore a finger source in some specific use cases, but independent of secondary clicks. Refs Genymobile#5055 <Genymobile#5055> Fixes Genymobile#5067 <Genymobile#5067> PR Genymobile#5076 <Genymobile#5076>
Environment
Describe the bug
When running
scrcpy.exe
with no flags, it works fine with the mouse. However, attempting to use the touchscreen either does not work at all or only sometimes works for a little bit.Adding the flag
--no-mouse-hover
causes touchscreen input to be captured again.The text was updated successfully, but these errors were encountered: