That's too low level. It's the android::InputDispatcher responsibility to shepherd events through android::InputChannels.
What is needed is something like a mir::input::Surface::consume_event(MirEvent) that, under
the hood, calls eventually android::InputDispatcher::notifyMotion(event,
surface->input_channel). Doing exactly what
MirSurfaceItem::dispatchTouchEventToMirInputChannel from lp:~unity-team/+junk
/qpa-mirserver does.
That's too low level. It's the android: :InputDispatche r responsibility to shepherd events through android: :InputChannels.
What is needed is something like a mir::input: :Surface: :consume_ event(MirEvent) that, under :InputDispatche r::notifyMotion (event, >input_ channel) . Doing exactly what :dispatchTouchE ventToMirInputC hannel from lp:~unity-team/+junk
the hood, calls eventually android:
surface-
MirSurfaceItem:
/qpa-mirserver does.