Closed J0Nreynolds closed 7 years ago
This is done by the platform by design. Confirmed also by https://developer.oculus.com/blog/developing-for-the-gear-vr-controller/.
What you could is filter out the touch events based on some criteria. Like tool type of value TOOL_TYPE_UNKNOWN and few other MotionEvent fields that probably identify the events uniquely.
Great, thanks for looking into this for me. I'll look into possible ways of ignoring the touch events.
Same issue as #1245. Touch/Motion events are being generated by button presses, yet they aren't originating from the GearCursorController. I'm currently working on setting motion events for the GearCursorController, but these aforementioned touch events often interrupt any touch events I generate. To reproduce this error, you can use the code in the previous issue:
Notice that pressing any of the buttons besides home or back on the GearVR Controller will dispatch a motion event of the form
MotionEvent { action=ACTION_MOVE, actionButton=0, id[0]=0, x[0]=1480.0, y[0]=720.0, toolType[0]=TOOL_TYPE_UNKNOWN ... }
The coordinates will always be (1480, 720), meaning there will always be a touch dispatched at that location.
I appreciate any help anyone can offer.