Re: No focus on map hint

[Rob Adams <robadams ucla edu>]

OK if people are satisfied with the suggestion I think that it should do
the trick.  Here is a patch:

--- wm-spec.sgml        2003-03-02 23:16:40.000000000 -0800
+++ wm-spec.sgml.no_focus       2003-03-14 09:20:07.000000000 -0800
@@ -1205,6 +1205,25 @@ _NET_WM_HANDLED_ICONS
        for iconified windows.
        </para>
     </sect2>
+       <sect2><title>_NET_WM_MAP_TIMESTAMP</title>
+       <programlisting><![CDATA[
+_NET_WM_MAP_TIMESTAMP CARDINAL/32
+]]></programlisting>
+       <para>
+Read by the window manager when the window is mapped. If the property
+is set to a non-zero value TIME, the application is declaring that the
+window was mapped due to a user action at server timestamp TIME. If
+set to a zero value the window was mapped for some other reason
+(i.e. not caused by the user directly).
+       </para>
+       <para>
+Rationale: This property allows a Window Manager to alter the focus,
+stacking, and/or placement behavior of windows when they are first
+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>


On Fri, 2003-03-14 at 08:39, Havoc Pennington wrote:
> On Fri, Mar 14, 2003 at 03:05:43PM +0100, Lubos Lunak wrote: 
> >  I like this, and I'm in favour of this.
> > 
> >  And in fact, I think it could help me to solve a little problem related to 
> > startup notification. In case you don't know, KDE has a feature that tries to 
> > avoid stealing focus, e.g. imagine you are typing in kwrite, then you decide 
> > to visit some www site, so you start Konqueror, and while waiting for 
> > Konqueror to start up, you keep typing in kwrite. Newly started Konqueror 
> > won't get focus and therefore won't interrupt the typing.
> > 
> >  The current implementation is basically just a hack, so I'd prefer this 
> > cleaner solution. The environment variable needed for it could be simply 
> > handled together with startup notification, so that wouldn't be a
> > problem.
> 
> The proposed property sounds fine to me, but I'm curious why startup
> notification doesn't work for this - it seems to me that it'd be
> perfectly reliable to do it via startup notification (I was planning
> to do it that way in fact).
> 
> Havoc
> _______________________________________________
> wm-spec-list mailing list
> wm-spec-list gnome org
> http://mail.gnome.org/mailman/listinfo/wm-spec-list
>