_NET_WM_PING

[Lubos Lunak <l lunak suse cz>]

 Hello,

 any comments on the attached patch? It wasn't explicitly specified, so I 
think it should be.

 Another issue I have is that if I strictly interpret the 'timestamp' field as 
X server timestamp, then I have trouble identifying the ping replies comming 
back. If I send several pings at the same time, how am I supposed to find out 
which reply matches which ping, when they all have root window as the window, 
and the timestamp is the same? Currently KWin uses the window ID as the 
"timestamp". Is that ok, or should I have the ID in data.l[2], and change the 
spec to say that the client mustn't modify anything in the event except for 
the target window when responding?

-- 
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 13:21:40.000000000 +0200
+++ wm-spec.sgml	2003-05-20 13:36:00.000000000 +0200
@@ -1243,7 +1243,8 @@ 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
+window immediately, by setting window = root, and calling XSendEvent
+with event mask SubstructureRedirectMask | SubstructureNotifyMask. The
 Client MUST NOT alter the timestamp, as this can be used by the Window Manager
 to uniquely identify the ping.
 		</para>