You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I believe the behaviour of InputQueue::pre_dispatch in v0.7 is wrong compared to v0.6, the ndk docs for AInputQueue_preDispatchEvent say this about the return value:
...Returns 0 if it was not pre-dispatched, meaning you can process it right now. If non-zero is returned, you must abandon the current event processing and allow the event to appear again in the event queue (if it does not get consumed during pre-dispatching).
Compared to the docs for the return value of AInputQueue_hasEvents (which the current version of InputQueue::has_events handles correctly):
Returns 1 if the queue has events; 0 if it does not have events; and a negative value if there is an error.
On the Quest 2, when the system menu is shown, the return value of AInputQueue_preDispatchEvent is -1 thus invoking the unreachable case. This does not happen with v0.6
The text was updated successfully, but these errors were encountered:
MarijnS95
changed the title
InputQueue::pre_dispatch v0.7 bug
[ndk 0.7.0] Allow any non-zero return code from AInputQueue_preDispatchEvent()Aug 2, 2022
Hello, I believe the behaviour of
InputQueue::pre_dispatch
in v0.7 is wrong compared to v0.6, the ndk docs forAInputQueue_preDispatchEvent
say this about the return value:Compared to the docs for the return value of
AInputQueue_hasEvents
(which the current version ofInputQueue::has_events
handles correctly):On the Quest 2, when the system menu is shown, the return value of
AInputQueue_preDispatchEvent
is -1 thus invoking the unreachable case. This does not happen with v0.6The text was updated successfully, but these errors were encountered: