Re: _NET_WM_PING



On Monday 09 of June 2003 17:12, Owen Taylor wrote:
> On Mon, 2003-06-09 at 10:45, Lubos Lunak wrote:
[snip]
>
> The change looks basically OK to me (I just fixed the infinite loop
> problem in GTK+, I'd have been unhappy with the first proposed to
> change"
>
> +The Client MUST NOT alter the timestamp or any other field in the
> event,
> +besides the window. The Window Manager can uniquely identify the ping
> by the timestamp
> +and the data.l[2] field if necessary.
>
> Would be slightly more grammatical if you said "any field in the
> event other than the window". I might actually be a bit more
> specific.
>
> "any field in the event other than the window. This includes all
> 5 longs in the data.l[5] array. The Window Manager can ...
> Note that some older clients may not preserve data.[2] through
> data.[4]"
>
> (I don't know of any clients that don't preserve these fields, but
> if we add extra requirements to the window manager spec, I think
> it's good practice to indicate that they are new)

 Hopefully final attempt.

-- 
Lubos Lunak
KDE developer
---------------------------------------------------------------------
SuSE CR, s.r.o.  e-mail: l lunak suse cz , l lunak kde org
Drahobejlova 27  tel: +420 2 9654 2373
190 00 Praha 9   fax: +420 2 9654 2374
Czech Republic   http://www.suse.cz/
--- wm-spec.sgml.sav	2003-05-20 14:42:55.000000000 +0200
+++ wm-spec.sgml	2003-06-09 17:24:15.000000000 +0200
@@ -1239,13 +1239,17 @@ message_type = WM_PROTOCOLS
 format = 32
 data.l[0] = _NET_WM_PING
 data.l[1] = timestamp
+data.l[2] = the respective client window
 other data.l[] elements = 0
 ]]></programlisting>
 		<para>
 A participating Client receiving this message MUST send it back to the root
-window immediately, by setting window = root, and calling XSendEvent.  The
-Client MUST NOT alter the timestamp, as this can be used by the Window Manager
-to uniquely identify the ping.
+window immediately, by setting window = root, and calling XSendEvent with
+the same event mask like all other root window messages in this specification use.
+The Client MUST NOT alter any field in the event other than the window. This
+includes all 5 longs in the data.l[5] array. The Window Manager can uniquely
+identify the ping by the timestamp and the data.l[2] field if necessary.
+Note that some older clients may not preserve data.l[2] through data.l[4].
 		</para>
 		<para>
 The Window Manager MAY kill the Client (using _NET_WM_PID) if it fails to


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]