Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!olivea!mintaka!bloom-beacon!LARRY.MCRCIM.MCGILL.EDU!mouse
From: mouse@LARRY.MCRCIM.MCGILL.EDU
Newsgroups: comp.windows.x
Subject: Re:  getting a "withdrawn" window back
Message-ID: <9008092301.AA16605@Larry.McRCIM.McGill.EDU>
Date: 9 Aug 90 23:01:18 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 39

> Here's a question that I hope someone can help me with.  There is a
> window that has a "window state" of withdrawn.  Is there any way to
> get that window un-withdrawn?

According to the ICCCM,

	o  Withdrawn -> Normal.  The client should  map  the  window
	   with WM_HINTS.initial_state being NormalState.
	
	o  Withdrawn -> Iconic.  The client should  map  the  window
	   with WM_HINTS.initial_state being IconicState.
	
	o  Normal -> Iconic.  The client should send a  client  mes-
	   sage event as described below.
	
	o  Normal -> Withdrawn.  The client should unmap the window,
	   and  follow  it  with  a  synthetic  UnmapNotify event as
	   described below.
	
	o  Iconic -> Normal.  The client should map the window.  The
	   contents of WM_HINTS.initial_state are irrelevant in this
	   case.
	
	o  Iconic -> Withdrawn.  The client should unmap the window,
	   and  follow  it  with  a  synthetic  UnmapNotify event as
	   described below.

I'm not including the "described below" stuff here; see the ICCCM for
that.

In your particular case, you may need to throw together a small program
to call XMapWindow (possibly poking the WM_HINTS property first) with a
window ID taken from the command line, since the problem is that the
client isn't taking care of things itself.

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu