-
-
Notifications
You must be signed in to change notification settings - Fork 22k
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
Incorrect behaviour for doubleclick on an Area2D on mobile devices #46101
Milestone
Comments
Possible related to #46100 |
@thebestnom Any thoughts on this issue? |
Weird, is it a regression? Did it worked before? It might be something that I that did I haven't noticed but I doubt it Anyone on it or I take the fix? |
@thebestnom Feel free to take the fix :) |
Btw, I had way less time on my hand that I though, Ill try to work on that tomorrow |
Ongnissim
added a commit
to Ongnissim/godot
that referenced
this issue
Oct 26, 2021
…and godotengine#46101. Changes the buttonMask for doubleTap input on android to recognize both Mouse and Screen Touch inputs.
This was referenced Sep 6, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Godot version:
3.2.3
OS/device including version:
Desktop test was Win 10.
Mobile test Android 11 on Galaxy S10e.
Issue description:
When double tapping an Area2D on mobile has incorrect behaviour compared to desktop:
doubleclick
property set to true, but has thepressed
property set to false, and it has a differentbutton_index
to the other press events in the sequence.Steps to reproduce:
With default project settings (i.e. "Emulate Touch As Mouse" is true):
Area2D
with an appropriateCollisionObject.
input_event
signal on theArea2D
object.doubleclick
,pressed
, andbutton_index
parameters.On Desktop the output for a double click is (4 events generated, press and release for each touch in the double click):
On mobile the output is as follows (notice the extra event, and the incorrect 2nd touch event).
Minimal reproduction project:
Testing-DoubleClickInput.zip
The text was updated successfully, but these errors were encountered: