From 443014db7c671fa721e7c5fd126309eb8a9b1321 Mon Sep 17 00:00:00 2001 From: Ian Douglas Scott Date: Fri, 8 Sep 2023 12:48:54 -0700 Subject: [PATCH] relative-pointer: Mention interaction with `wl_pointer.frame` XWayland assumes relative motion events are followed by a `frame` if `wl_pointer` has version 5 or greater: https://gitlab.freedesktop.org/xorg/xserver/-/blob/master/hw/xwayland/xwayland-input.c But the protocol didn't mention `frame`. This may be implied, but should be addressed specifically. This should match existing implementations. Signed-off-by: Ian Douglas Scott --- unstable/relative-pointer/relative-pointer-unstable-v1.xml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/unstable/relative-pointer/relative-pointer-unstable-v1.xml b/unstable/relative-pointer/relative-pointer-unstable-v1.xml index ca6f81d..6d66752 100644 --- a/unstable/relative-pointer/relative-pointer-unstable-v1.xml +++ b/unstable/relative-pointer/relative-pointer-unstable-v1.xml @@ -114,6 +114,10 @@ relative motion. The order of an absolute and relative motion event originating from the same physical motion is not guaranteed. + If wl_pointer has version 5 or later, relative motion will be followed + by wl_pointer.frame. If sent in combination with wl_pointer.motion, + both will be part of the same frame. + If the client needs button events or focus state, it can receive them from a wl_pointer object of the same seat that the wp_relative_pointer object is associated with.