Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!ames!haven!mimsy!mojo!stripes
From: stripes@eng.umd.edu (Joshua Osborne)
Newsgroups: comp.windows.x
Subject: Re: ICCCM question about raising windows
Message-ID: <1990Apr12.025258.15374@eng.umd.edu>
Date: 12 Apr 90 02:52:58 GMT
References: <9004092038.AA07859@sae.com>
Sender: news@eng.umd.edu (The News System)
Organization: Maryversity of Uniland, College Park
Lines: 20

In article <9004092038.AA07859@sae.com> mikeo@sae.UUCP (Michael Ovington) writes:
>   We have an application that can, at the user's request, generate multiple
>   top level windows (with XtCreatePopupShell). If the user doesn't delete
>   these windows, older windows can become obscured by newly created ones.
[...]
>   I don't see this situation covered in the ICCCM. If it is, could someone
>   please quote me chapter and verse. If my workaround shouldn't be used,
>   could someone suggest a portable way for communicating the raise request
>   to the window manager?
Have you tried withdrawing the window, then un-withdrawing it (what is the
un-withdrawed state called?  Normal?).  That's legal ICCCM, not that a
window manager will be able to (easily) figure out that this is a restacking
request it should work most of the time....       (if you find a ICCCM
restack use it, forget I said this, etc.)
-- 
           stripes@eng.umd.edu          "Security for Unix is like
      Josh_Osborne@Real_World,The          Mutitasking for MS-DOS"
      "The dyslexic porgramer"                  - Kevin Lockwood
"Don't try to change C into some nice, safe, portable programming language
 with all sharp edges removed, pick another language."  - John Limpert