Skip to content
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

Release InputEvent event doesn't match with move event on Android #41585

Open
ricochet1k opened this issue Aug 28, 2020 · 2 comments
Open

Release InputEvent event doesn't match with move event on Android #41585

ricochet1k opened this issue Aug 28, 2020 · 2 comments

Comments

@ricochet1k
Copy link

ricochet1k commented Aug 28, 2020

Godot version:

3.2 branch after rc4: 6b5102c
Also happens on 3.2.3.rc4

OS/device including version:

Android Pixel 2, GLES3

Issue description:

The position of the touch release event on Android doesn't match the last motion event, but only for swipes that move left, or up. Right and down swipes work fine.

It seems related to the code to adjust input events based on the control's position, without the white rectangle above this doesn't happen.

Steps to reproduce:
Export the repro project to an android device. Touch the screen, drag to the left, let go. Blue square should be centered in the green square, but you'll see that it is offset downwards by the same height as the white rectangle. (there is a white rectangle at the top of the screen, it's hard to see because it blends in with the page.) Red is the touch down event, green is the last move event, blue is the touch up event.
Screenshot_20200828-145917

Strangly, swipes to the right work as expected:
Screenshot_20200828-145933

Minimal reproduction project:

android_touch_bug.zip

@ricochet1k
Copy link
Author

Also related: Trying to isolate this further into whether it's mouse or touch events, I find that InputEventScreenTouch is never sent with pressed == false, so there is no event for touch release.

@Sauermann
Copy link
Contributor

I have tried to replicate this problem in v4.0.beta.custom_build [e82d66f] but this issue is no longer reproducible. Can't say anything about v3.x.

@Calinou Calinou added this to the 3.x milestone Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants