Re: No focus on map hint II.
- From: Lubos Lunak <l lunak suse cz>
- To: Owen Taylor <otaylor redhat com>
- Cc: wm-spec-list gnome org
- Subject: Re: No focus on map hint II.
- Date: Mon, 9 Jun 2003 17:12:18 +0200
On Wednesday 04 of June 2003 17:38, Owen Taylor wrote:
> On Tue, 2003-06-03 at 08:43, Lubos Lunak wrote:
> > On Friday 30 of May 2003 18:07, Owen Taylor wrote:
[comments snipped]
Another attempt for _NET_WM_USER_TIME is attached, with the CARDINAL[] hack
removed, and changing the wording for user interaction to not strictly
specify only core input events.
Ok now?
--
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:05:17.000000000 +0200
@@ -1214,6 +1214,38 @@ _NET_WM_HANDLED_ICONS
for iconified windows.
</para>
</sect2>
+ <sect2><title>_NET_WM_USER_TIME</title>
+ <programlisting><![CDATA[
+_NET_WM_USER_TIME CARDINAL/32
+]]></programlisting>
+ <para>
+This property contains the XServer time at which last user activity in this
+window took place.
+ </para>
+ <para>
+Clients should keep the last timestamp from user interaction. and set
+this timestamp in this property on every new toplevel window before mapping it.
+A client that only deals with core events, might, for example, use the
+timestamp of the last KeyPress, ButtonPress, or ButtonRelease
+event. KeyRelease events should not generally be considered to
+be user interaction, because an application may receive KeyRelease
+events from global keybindings. Clients should start setting the property
+only after receiving the first event from user interaction, they shouldn't set
+it before receiving first input event. The special value of zero on a newly
+mapped window means that the window shouldn't initially get focus after being mapped.
+ </para>
+ <para>
+If the client has the active window, it should also update this property
+on the window whenever there's user activity.
+ </para>
+ <para>
+Rationale: This property allows a Window Manager to alter the focus,
+stacking, and/or placement behavior of windows when they are
+mapped depending on whether the new window was created by a user
+action or is a "pop-up" window activated by a timer or some other
+event.
+ </para>
+ </sect2>
</sect1>
<sect1>
<title>Window Manager Protocols</title>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]