Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!udel!haven!decuac!bacchus.pa.dec.com!wsl.dec.com!klee
From: klee@wsl.dec.com (Ken Lee)
Newsgroups: comp.windows.x
Subject: Re: Forking a process and allowing both to use the window
Keywords: fork, event queue,
Message-ID: <1990Nov14.113031@wsl.dec.com>
Date: 14 Nov 90 19:30:31 GMT
References: <{-*^W|-@rpi.edu>
Sender: news@wrl.dec.com (News)
Reply-To: klee@wsl.dec.com
Organization: DEC Western Software Laboratory
Lines: 16

In article <{-*^W|-@rpi.edu>, mittmann@ral.rpi.edu (Michael Mittmann) writes:
|> Someone must have tried this before.  Is it hopeless?  Should I use
|> pipes (or X-properties) to send messages to a single process which
|> controls the window?  Should I just give up, and write the event
|> checking into the main loop of the other program?

Two processes can share a window, but should not try to use the same
server connection.  Try opening a second connection from the child
process.  You can use any X resource (except GCs) on any connection to
the same X server.

-- 
Ken Lee
DEC Western Software Laboratory, Palo Alto, Calif.
Internet: klee@wsl.dec.com
uucp: uunet!decwrl!klee