Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!lll-winken!aunro!alberta!ubc-cs!news.UVic.CA!ale!caughey
From: caughey@ale.UVic.CA (Dave  Caughey)
Newsgroups: comp.windows.open-look
Subject: Closing Autonomous Windows
Message-ID: <1991Jun12.001244.5041@sol.UVic.CA>
Date: 12 Jun 91 00:12:44 GMT
Sender: news@sol.UVic.CA
Reply-To: caughey@ale.UVic.CA (Dave  Caughey)
Organization: University of Victoria, Victoria, BC, Canada
Lines: 41
Nntp-Posting-Host: ale.uvic.ca


I have developed a number of X applications which spawn other
processes.  I would like to be able to control those spawned-processes'
windows from my applications.

For example, by clicking on a button, I spawn an xterm.  On subsequent
clicks, I would like to bring it to the front by calling XRaiseWindow,
or close it with XIconifyWindow.

Now, I presume that (one way) I can get the window ID of an autonomous
window is to have my application cal XGrabPointer, and then clicking on
the target window.

It seems that I could then call XIconifyWindow and thus close it.  The
routine returns a code indicating success in sending the message, but
nothing happens.

Now, O'Reilly states that "window managers may elect to receive this
message" (Vol 2, page 284).

So I have a couple questions:

	1) Does OLWM recognize such requests?
		If so, what am I doing wrong?
		If not, can it be made to?

	2) Does TWM?

	3) Am I way off-base in my approach to this problem?


The development environment is as follows: 
    OpenWindows 2.0, OLWM, SparcStation, and (sigh) DevGuide

Thanks much,
Dave
___________________________________________________________________________
Dave Caughey				Dept. of Elec. & Comp. Engineering
caughey@sirius.uvic.ca			P.O. Box 3055
					University of Victoria		  
"10 million lemmings can't be wrong"	Victoria, B.C., CANADA V8W 3P6