-
Notifications
You must be signed in to change notification settings - Fork 311
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
onPinch breaking on control + scroll #641
Comments
I tried and can't reproduce. What mouse are you using? Not sure what I'm supposed to look at in the video btw. |
I am using Logitech M650. In the video I wanted to highlight that the movement[0] is assigned a NaN value on control + scroll. Once the 0th index of movement is assigned NaN, the gesture stops working |
Btw it is not mouse specific |
Hm in your code there is supposed to be an alert when the movement is NaN... I don't see it in the video. |
Hmmm, let me share a new video use-ges-pinch.mov |
I am experiencing the same issue on a similar setup: Use Gesture version: 10.3.1 When scrolling down (and vice versa for scrolling up), |
In the following screenshot, I log the In the next screenshot, I have been scrolling fast. Notice how large the values are: If I keep scrolling, I encounter I think it has to do with scroll acceleration on MacOS:
When scrolling with the Logitech M3 mouse, I get very large If so, one could claim that this is not a bug in the library. On the other hand, if you use various tools like Miro and Figma, you'll notice that they've somehow solved it. Or perhaps I am using the |
@Khush08, I can avoid the worst effects (Infinites and
|
Describe the bug
The onPinch gesture starts breaking while using control + scroll. The movement property on the onPinch state has a NaN value at the Oth index. The onPinch gesture completely stops working after that
Sandbox or Video
https://codesandbox.io/s/fancy-rgb-x959zf?file=/src/App.js
pinch.mov
Steps to reproduce - Try zooming the blue box using control + mouse scroll wheel multiple times
Information:
The text was updated successfully, but these errors were encountered: