From 231908869bd89e83ff73129d9cbdf040dce1cf4c Mon Sep 17 00:00:00 2001 From: lunakl Date: Tue, 29 Jul 2003 18:04:19 +0000 Subject: _NET_WM_USER_TIME --- wm-spec/wm-spec.xml | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/wm-spec/wm-spec.xml b/wm-spec/wm-spec.xml index b789d51..05613c9 100644 --- a/wm-spec/wm-spec.xml +++ b/wm-spec/wm-spec.xml @@ -1266,6 +1266,38 @@ _NET_WM_HANDLED_ICONS for iconified windows. + _NET_WM_USER_TIME + + +This property contains the XServer time at which last user activity in this +window took place. + + +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. + + +If the client has the active window, it should also update this property +on the window whenever there's user activity. + + +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. + + Window Manager Protocols -- cgit v1.2.3-70-g09d2