Don't run haptic feedback when the UI is rendered. - #1069
Merged
Merged
Conversation
austincondiff
requested review from
austincondiff,
lukepistrol and
thecoolwinter
February 20, 2023 06:30
austincondiff
approved these changes
Feb 20, 2023
matthijseikelenboom
approved these changes
Feb 20, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
We are running haptic feedback when the isSnapped flag is set. This flag gets set when the UI is first rendered. Fix is to ignore the first render i.e. do not run the haptic feedback.
Related Issue
Checklist