From ed7f0952943492769f1ef89b01fac09a0eeaac99 Mon Sep 17 00:00:00 2001
From: probonopd <probono@puredarwin.org>
Date: Sun, 30 Mar 2025 15:03:46 +0000
Subject: [PATCH] Remove `configured` event, use `placement_state` instead

---
 .../ext-toplevel-placement-v1.xml             | 38 ++++++++-----------
 1 file changed, 15 insertions(+), 23 deletions(-)

diff --git a/staging/ext-toplevel-placement/ext-toplevel-placement-v1.xml b/staging/ext-toplevel-placement/ext-toplevel-placement-v1.xml
index d68ce0e..e94601c 100644
--- a/staging/ext-toplevel-placement/ext-toplevel-placement-v1.xml
+++ b/staging/ext-toplevel-placement/ext-toplevel-placement-v1.xml
@@ -95,32 +95,15 @@
         ideally be sent before the first wl_surface.commit that maps the window.
         Compositors are unlikely to substantially alter placement based on
         suggestions sent after the window is already mapped and positioned.
+
+        This request causes the compositor to send the placement state, including
+        the output and logical coordinates where the toplevel is currently placed.
       </description>
       <arg name="output" type="object" interface="xdg_output" summary="target output"/>
       <arg name="x" type="int" summary="suggested logical x coordinate relative to output"/>
       <arg name="y" type="int" summary="suggested logical y coordinate relative to output"/>
     </request>
 
-    <event name="configured">
-       <description summary="notify client of final placement outcome">
-         This event notifies the client of the output and logical position where
-         the compositor has actually placed the window, typically sent during
-         the initial configuration sequence after considering any placement
-         suggestions.
-
-         This allows the client to know the result of its suggestion and update
-         its stored state accurately. Compositors are not required to send this
-         event if no suggestion was made or considered relevant to the final
-         placement decision.
-
-         Standard xdg_toplevel.configure events remain the primary source for
-         ongoing size, state, and potentially position updates.
-       </description>
-       <arg name="output" type="object" interface="xdg_output" summary="output the window is ultimately placed on"/>
-       <arg name="x" type="int" summary="final logical x coordinate relative to output"/>
-       <arg name="y" type="int" summary="final logical y coordinate relative to output"/>
-    </event>
-
     <request name="get_placement_state">
       <description summary="request the current placement state">
         Requests the compositor to send the current placement state, including
@@ -130,9 +113,18 @@
 
     <event name="placement_state">
        <description summary="notify client of current placement state">
-         This event provides the current output and logical position where
-         the compositor has placed the window. It is sent in response to a
-         `get_placement_state` request.
+         This event notifies the client of the output and logical position where
+         the compositor has actually placed the window, typically sent during
+         the initial configuration sequence after considering any placement
+         suggestions, and in response to a `get_placement_state` request.
+
+         This allows the client to know the result of its suggestion and update
+         its stored state accurately. Compositors are not required to send this
+         event if no suggestion was made or considered relevant to the final
+         placement decision.
+
+         Standard xdg_toplevel.configure events remain the primary source for
+         ongoing size, state, and potentially position updates.
        </description>
        <arg name="output" type="object" interface="xdg_output" summary="output the window is currently placed on"/>
        <arg name="x" type="int" summary="current logical x coordinate relative to output"/>