Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-beacon!dont-send-mail-to-path-lines
From: Dave.Rosenthal@eng.sun.COM (David Rosenthal)
Newsgroups: comp.windows.x
Subject: Re: How do I give a popup window a title?
Message-ID: <9105102049.AA03697@devnull.Eng.Sun.COM>
Date: 10 May 91 20:44:14 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 31

> The ICCCM is not entirely clear, to me, on this point: how much are
> window managers permitted to meddle with override-redirect windows?

............

> 	o If the window will be visible for a very short time, and
> 	  should not be decorated at all, the client can set
> 	  override-redirect on the window.  In general, this should be
> 	  done only if the pointer is grabbed while the window is
> 	  mapped.  The window manager will never interfere with these
> 	  windows, which should be used with caution.  An example of an
> 	  appropriate use is a pop-up menu.
> 
> It's not clear just what "interfere with" means.  I would assume it
> means that the window manager will not do anything with the window,
> including reparenting and decorating, but it doesn't quite *say* that.

It certainly says that override-redirect windows are not to be decorated:

> 	o If the window will be visible for a very short time, and
> 	  should not be decorated at all, the client can set
          ^^^^^^^^^^^^^^^^^^^^^^^

An ICCCM-compliant window manager will not do anything to ("will
never interfere with") to override-redirect windows.  And please
don't think this is a wonderful opportunity for clients to enforce
decisions about the user interface on the window manager.  The
cautions about not using override-redirect except under specific
conditions should be carefully observed.

	David.