Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!uflorida!gatech!ncsuvx!news
From: george@hobbes.ncsu.edu (George Browning)
Newsgroups: comp.windows.x
Subject: Re: "wake up" XtAppMainLoop (X <-> C IPC)
Keywords: XtAddInput, sockets
Message-ID: <1990Oct24.124130.3273@ncsuvx.ncsu.edu>
Date: 24 Oct 90 12:41:30 GMT
References: <9954@uhccux.uhcc.Hawaii.Edu> <12053@ibism.uucp>
Reply-To: george@hobbes.ncsu.edu (George Browning)
Organization: NCSU Computing Center
Lines: 27

>Create a pipe for communicating with your child.  Your child writes to
>the pipe and your parent calls XtAddInput with the XtInputReadMask.  When
>data appears on the pipe the function specified by XtAddInput will be 
>executed.  You then read() on the pipe.  Be careful to check that
>data has come across the pipe. 
>
>-- 
>
>Larry Poleshuck

How would use use XtAddInput with Unix inter-process communication?
I need to use some System V IPC routines so a X parent interface can
talk with its Unix 'C' child program.

The X interface forks off the child C program and I utilize the above
piping to capture the output of the C program.  However, when an error
occurs I'd like to pass a message from the C program to the X interface
telling it to display an error dialog.

Thanks for any help,
george

--
------------------------------------------------------------------------
| o |  George Browning                 george@hobbes.catt.ncsu.edu | o |
| o |  NC State University             Raleigh, NC                 | o |
------------------------------------------------------------------------