This repository has been archived by the owner on Nov 30, 2022. It is now read-only.
Fix for wrong offset values when onDoubleTapAfter is fired #61
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.
This is fix for Problem statement #60
I have moved the
onDoubleTapAfter
intothis.setState
call back. this will ensure user will get correct offsetX and offsetY.Please review, we're using this component in one of our project and this fix will help us to deliver bug free code.
Appreciate your efforts. :)