The value `touchEvent.locationX` equals NaN or INF and will be replaced by `0`.
See original GitHub issue💘 Very nice lib and thanks for sharing it! ❤️
Do you think it be possible to fix console.warn
messages when reaching 90deg
while dragging?
Produced warning at 90deg
:
The value 'touchEvent.locationX' equals NaN or INF and will be replaced by '0'.
Same apply also for touchEvent.locationY
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
React native get the coordinates of my touch event
With TouchableOpacity you have the onPress prop that is passed a press event. From this press event you have access to the x,y...
Read more >JavaScript isNaN() Method - W3Schools
The isNaN() method returns true if a value is NaN. The isNaN() method converts the value to a number before testing it. See...
Read more >fl_chart | Flutter Package - Pub.dev
They are ordered based on their distance to the touch event and also contain that distance. 0.41.0 #. BUGFIX Fix getNearestTouchedSpot. Previously it...
Read more >QTest Namespace | Qt Test 6.4.1 - Qt Documentation
QTest::QTouchEventWidgetSequence, touchEvent(QWidget *widget, ... See the Qt Test Overview for information about how to write unit tests.
Read more >Node (JavaFX 8) - Oracle Help Center
minY location that should be used when this node is being vertically ... by a change to the clip variable, the change is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thank you ignoring the log is fine for now , but it’s better to create an issue on Facebook react native repository if there isn’t one yet? I forgot to create one
Oh sorry! Sounds like a rn core issue then because I’m getting the exact problem on -90 or 90 with
react-native-reanimated