Re: No focus on map hint

[Marko Macek <Marko Macek gmx net>]

Havoc Pennington wrote:

> On Fri, Mar 14, 2003 at 09:22:52AM -0800, Rob Adams wrote:
>  
>
> > 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>
> >
> >    
>
> Could we also add text like:
>
> When launching an application, the DESKTOP_LAUNCH_TIMESTAMP
> environment variable may be set to the timestamp of the user action
> causing the launch. Applications may choose to honor this environment
> variable by setting _NET_WM_MAP_TIMESTAMP to its
> contents. Applications should unset the environment variable after
> using it, to avoid transmitting it to their child processes.
>  

I fully support the above. This is something I wanted in icewm for a 
while now.

Hmm. Could this also be used to open the windows on the right workspace, 
even after the user has switched away?
The window manager would have to keep a history of workspace switches... 
Is there a better way?

MArk