Using onPointerDown or onClick on a mesh with React Native running on Android has the following behavior. Assume three meshes A, B, and C:
Scenario 1:
Touch mesh A - event is successfully triggered on A.
Touch mesh B - event is triggered on A again unexpectedly, and then a second event is triggered on B.
Touch mesh C - event is triggered on B again unexpectedly, and then a second event is triggered on C.
Scenario 2:
Touch mesh A - event is successfully triggered on A.
Touch empty area anywhere - event is unexpectedly triggered on A again.
Touch mesh B - event is successfully triggered on B.
Touch empty area anywhere - event is unexpectedly triggered on B again.
Touch mesh C - event is successfully triggered on C.
So this very nearly works, but not quite. Is there a solution that doesn't involve a hack to check if two events are fired in rapid succession and ignoring the first?
that would need someone to take a look at it. RN came in by contribution and i have no experience with it myself, wouldn't even know how to test it. it's under src/targets/native
I will take a look
I'm seeing this same problem FWIW
Most helpful comment
I will take a look