-
Notifications
You must be signed in to change notification settings - Fork 3
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
M2-7967: fix input tap detection #876
Conversation
…on event fire correctly
…oving from Game Manager
In this PR I left a lot of comment in the code to facilitate the test, but it will be removed once it get approved. |
I left a lot of comment to facilitate the understanding, once it get approved I will remove all comments. |
comments removed |
…ementing setEndTimeViewingImage that allows it to capture precise timing information for each phase of your game, Increment countTest Before Checking isEndGame,adjusting isEndGame method ...
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.
Tested and input detection is running great now, I have a few questions about the changes you introduced.
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.
Thanks @felipeMetaLab
Tested multiple runs and all taps appear registered correct now.
📝 Description
🔗 Jira Ticket M2-7967
Solution Explanation:
this is a continuation of #870.
This time I am handling the enable and disable button.
📸 Screenshots
Simple Choice Reaction Time task:
test.reaction.mov
🪤 Peer Testing
Before:
Input will be ignored the longer you wait to tap the button (disabled state)
Expected:
now you will be able to click all the times.