From 275fce4af9b6008a372933dfa5109553e6348dd1 Mon Sep 17 00:00:00 2001 From: Mikhail Gusarov Date: Fri, 21 Oct 2022 00:17:38 +0200 Subject: xdg-shell: Clarify relationship between [un]set_maximized and configure Make it explicit in the protocol that [un]set_maximized and the following configure event can't be reliably matched, and the clients shouldn't try to do it. Closes #106 Signed-off-by: Mikhail Gusarov --- unstable/xdg-shell/xdg-shell-unstable-v5.xml | 10 ++++++++++ unstable/xdg-shell/xdg-shell-unstable-v6.xml | 10 ++++++++++ 2 files changed, 20 insertions(+) (limited to 'unstable') diff --git a/unstable/xdg-shell/xdg-shell-unstable-v5.xml b/unstable/xdg-shell/xdg-shell-unstable-v5.xml index ef0180d..59fa9de 100644 --- a/unstable/xdg-shell/xdg-shell-unstable-v5.xml +++ b/unstable/xdg-shell/xdg-shell-unstable-v5.xml @@ -478,6 +478,11 @@ If the surface was already maximized, the compositor will still emit a configure event with the "maximized" state. + + Note that unrelated compositor side state changes may cause + configure events to be emitted at any time, meaning trying to + match this request to a specific future configure event is + futile. @@ -500,6 +505,11 @@ If the surface was already not maximized, the compositor will still emit a configure event without the "maximized" state. + + Note that unrelated compositor side state changes may cause + configure events to be emitted at any time, meaning trying to + match this request to a specific future configure event is + futile. diff --git a/unstable/xdg-shell/xdg-shell-unstable-v6.xml b/unstable/xdg-shell/xdg-shell-unstable-v6.xml index dfaf784..7fb4658 100644 --- a/unstable/xdg-shell/xdg-shell-unstable-v6.xml +++ b/unstable/xdg-shell/xdg-shell-unstable-v6.xml @@ -827,6 +827,11 @@ If the surface was already maximized, the compositor will still emit a configure event with the "maximized" state. + + Note that unrelated compositor side state changes may cause + configure events to be emitted at any time, meaning trying to + match this request to a specific future configure event is + futile. @@ -849,6 +854,11 @@ If the surface was already not maximized, the compositor will still emit a configure event without the "maximized" state. + + Note that unrelated changes in the state of compositor may cause + configure events to be emitted by the compositor between processing + this request and emitting corresponding configure event, so trying + to match the request with the event is futile. -- cgit v1.2.3