Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!decwrl!ucbvax!MN.ECN.PURDUE.EDU!tongz
From: tongz@MN.ECN.PURDUE.EDU (Tong Zheng)
Newsgroups: comp.windows.x
Subject: X routines running on child processes
Message-ID: <9007281621.AA07911@mn.ecn.purdue.edu>
Date: 28 Jul 90 16:21:47 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: General Consultant, ME Comp. Lab
Lines: 31


Here is a problem I met when I try to integrate a program
into X.  The program looks like this:

After the program starts, it generates two child processes,
first one does normal purpose of this program, the second one
runs X rountines to generate a graphical interface. They
communicate each via signal and pipe. Second process which 
runs X rountines keep updating the screen whenever it recieves
signal from the first process.  Then the parent(main) process
exists, leaves two child processes alive(running on background).
All communications work fine, the process contains X part 
is able to receive the signal from the first process and
to update the screen, e.g, change the XtNlabel for a label widget.
The problem is that all changes are not seen on the window
until I move the cursor to the window.

I am running R4 on a SUN4 and using twm.  Anyone has any idea
about why this happens? The process running X is self contained,
all widgets are Managed.

Any help is appreciated!!



---

| Zheng, Tong                  | major: Computer Science   |
|  - student programmer, Mechanical Eng., Purdue University|
| ARPA: tongz@mn.ecn.purdue.edu  BITNET: xdpc@puccvm.BITNET|
------------------------------------------------------------