Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!bcm!etaylor
From: etaylor@wilkins.iaims.bcm.tmc.edu (Eric Taylor)
Newsgroups: comp.windows.x
Subject: Re: Parent window
Message-ID: <3236@gazette.bcm.tmc.edu>
Date: 18 Dec 90 16:02:59 GMT
References: <1990Dec17.135127.867@nas.nasa.gov>
Sender: usenet@bcm.tmc.edu
Reply-To: etaylor@wilkins.iaims.bcm.tmc.edu (Eric Taylor)
Organization: Baylor College of Medicine, Houston, Tx
Lines: 22
Nntp-Posting-Host: wilkins.iaims.bcm.tmc.edu


In article <1990Dec17.135127.867@nas.nasa.gov>, parlette@nas.nasa.gov (Edward B. Parlette) writes:
|> 
|> 
|> From within my client program I would like to be able to
|> pop my 'parent window' forward.  (By 'parent window' I mean the
|> xterm window that the user used to start my program).  This would
|> allow me to use stderr and stdout for writing error messages. ( I know
|> there are better ways of informing the user of errors but for 
|> other reasons I need to be able to do this. )  Thanks for any info.

The xterm window has no relationship to the X application
you ran.  It is not a 'parent window'.  It do not believe 
there is any kind of link from your application to the
window id of the xterm that brought it up.  I . E.  an xterm
from an entirely different display could have brought up 
your application.
--
					Eric Taylor
					Baylor College of Medicine
					etaylor@wilkins.bcm.tmc.edu
					(713) 798-3776