-
67b70d2f
by Twaik Yont at 2026-05-19T23:19:09+02:00
wineandroid: Restrict Java keyboard focus to whole Wine views.
Client Wine views are rendering targets for GL/Vulkan client surfaces.
They should not become independent Android keyboard focus targets,
because input is dispatched by Wine window state, not by the rendering
surface itself.
Make client Wine views non-focusable and keep keyboard focus on the
whole Wine view. Pointer/key input can then be handled by the parent
Wine window while the client view remains only a drawable surface.
Signed-off-by: Twaik Yont <9674930+twaik@users.noreply.github.com>
-
f671662b
by Twaik Yont at 2026-05-19T23:19:09+02:00
wineandroid: Focus the desktop view after creating it.
Android key events are delivered to the focused view before Wine turns
them into hardware input. Request focus for the desktop whole view after
it is added, so keyboard input works immediately after activity startup
without relying on a later focus transition such as switching through
Recents.
Signed-off-by: Twaik Yont <9674930+twaik@users.noreply.github.com>
-
762112fe
by Twaik Yont at 2026-05-19T23:19:09+02:00
wineandroid: Ignore duplicate primary button motion events.
Some Android devices report primary mouse button clicks through both
touch down/up and generic motion button press/release events. Forwarding
both paths to Wine produces duplicate mouse button input, which can
desynchronize button state and interfere with capture or window
activation after dragging windows.
Ignore generic motion primary button press/release events and keep using
the touch path for the primary button. Leave non-primary buttons on the
generic motion path, since they may not be reported as touch events.
Signed-off-by: Twaik Yont <9674930+twaik@users.noreply.github.com>