Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!think.com!barmar
From: barmar@think.com (Barry Margolin)
Newsgroups: comp.windows.x
Subject: Re: running other processes with windows
Message-ID: <1991Feb7.011418.20345@Think.COM>
Date: 7 Feb 91 01:14:18 GMT
References: <1991Feb6.193011.13870@intelhf.hf.intel.com> <1991Feb6.223302.25752@agate.berkeley.edu>
Sender: news@Think.COM
Organization: Thinking Machines Corporation, Cambridge MA, USA
Lines: 18

In article <1991Feb6.223302.25752@agate.berkeley.edu> brp@bandit.berkeley.edu (Bruce Raoul Parnas) writes:
>  I
>would like to have my procedure be the main job, and be able to output status in
>a widget.  i now send output via printf to the window from which i invoked the
>routine, and would simply like to redirect this output to a widget that i open,
>without seriously affecting my ability to perform the main computation.

If you're using Unix, you could fork a child process that can create the
widget.  Create a pipe, and use fprintf to send the status into the pipe.
The child process reads from the pipe while in its main loop, and copies
any input to the widget.


--
Barry Margolin, Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar