Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!ucsd!ucbvax!alfalfa.com!nazgul
From: nazgul@alfalfa.com (Kee Hinckley)
Newsgroups: comp.windows.x.motif
Subject: Re: raising a widget
Message-ID: <910201184132.388@alphalpha>
Date: 1 Feb 91 23:41:32 GMT
References: <9102011821.AA03346@shasta.tivoli.com>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 18

> 
> You should read ICCCM and learn why client programs should NOT attempt to
> control (top-level) window stacking order.
> 
> The rationale:	All rights to top-level window configuration belong to the User
> King and should not be usurped by pesky clients. The tool through which the User
> King exerts these rights is the window manager. 
For all rules there are exceptions.  The reason we do a raise is
that the user has just asked for a compose window so they can send
mail.  We cache the compose window and remap it on request.  At least
one WM keeps the stacking order the way it was before the window
was unmapped - which may place it behind existing windows.  The user's
intent was clearly to place it on top, so we do.  On most WMs though
the request is a noop, since it's already there.

In general though, I agree, and in fact the code I sent won't work
if the widget has been reparented - which is fine, since the only
case we care about is a non-reparenting window manager :-).