Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!uunet!mcsun!unido!pbinfo!asterix!kern
From: kern@asterix.cadlab.de (Thomas Kern)
Newsgroups: comp.windows.x.motif
Subject: Re: Re:Attaching an X window process to a previously running X window pro
Message-ID: <1991Jun10.080252.8346@uni-paderborn.de>
Date: 10 Jun 91 08:02:52 GMT
Article-I.D.: uni-pade.1991Jun10.080252.8346
References: <9106071436.AA21149@ucbvax.Berkeley.EDU>
Sender: news@uni-paderborn.de (News Uni-Paderborn)
Organization: Cadlab
Lines: 34
Nntp-Posting-Host: 131.234.80.150

In article <9106071436.AA21149@ucbvax.Berkeley.EDU>, E_CMA@vaxa.nerc-murchison.ac.uk writes:

[ stuff deleted ]

|> In essence seperate processes can communicate with each other via
|> Atoms using Property Notify Events. Your "child" application defines
|> an Atom with the same name and display i.d. as one defined by the main
|> application and does a XChangeProperty on it. This is picked up by
|> the main applications event loop where the PropertyChangeMask has been 
|> set using XSelectInput to allow the main application to "receive"

Not quite correct: Atoms are used to name Properties. You may call
XChangeProperty and XSelectInput for a Property, not for an Atom.

|> Data can be retrieved from the Atom by any client for which it is 
|> defined using XGetWindowProperty.

Data can't be retrieved from an Atom. Atoms are nothing more than names 
(strings!) stored in the X-Server. You may read data from a Property named 
by an Atom. That's why those functions have the word 'property' in their names.

|> Cheers
|>    Carolyn

Thomas

-- 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Thomas Kern       |       Tel.  : (+49) (+) 5251-284 111                 |
| CADLAB            |       Fax   : (+49) (+) 5251-284 140                 |
| Bahnhofstr. 32    |       E-Mail: kern@cadlab.uucp                       |
| D-4790 Paderborn  |               kern@cadlab.cadlab.de                  |
| Germany           |               ...!uunet!unido!cadlab!kern            |
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~