-
-
Notifications
You must be signed in to change notification settings - Fork 21.1k
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
Fix Android logic for deferred window input events being inverted #83301
Fix Android logic for deferred window input events being inverted #83301
Conversation
672b9ce
to
e757fa2
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Great work on this PR (helped me work out what was likely going wrong) - I think there is a better way to fix, as this PR will introduce a tick delay in input. See #66318 (comment) EDIT: Just clear any confusion, this comment refers to previous version of the PR, author has since changed the commit significantly. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
660efb8
to
458b32e
Compare
PR concerned is #51597 . Pinging @RandomShaper . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤦♂️
Great spot @Alex2782 ! 👍 EDIT: Actually the commit message is not that bad, I'm sure production team will say if they prefer different wording. I try to include in the commit message what the PR actually does (prevents deferred call bug). For future reference it's fine to open multiple PRs using different approaches, and close previous ones as you find a better approach. |
I amended the PR title to match what the actual bug was, and not one of its prominent symptoms. The commit message could be amended similarly, but it's not critical. Edit: I amended the commit message myself as I want to merge this now for 4.2 beta 3. |
Notably fixes issues with `is_action_just_*` queries in `_physics_process` for TouchScreenButton. Fixes godotengine#66318. Fixes godotengine#82396.
458b32e
to
5137497
Compare
Thanks! |
Cherry-picked for 4.1.3. Note that without #79341 the code was different, so I had to remake the changes. It's unlikely that we would make another 4.0.x release, but if we do, the same changes need to be remade there. |
Workaround / Fixes #82396 (comment) #66318
maybe more: Github search
Bugsquad edit:
physics_frames
comparison atTouchScreenButton
is not always possible. input.cpp#L306TouchScreenButton::_press
is mostly triggered after_physics_process
.The change should have no effect on
Input Map actions
: input.cpp#L716Minimal test project: test.zip
Screen_recording_20231022_030544.mp4