Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-beacon!dont-send-mail-to-path-lines
From: tomt@maui.coral.COM (Tom Tulinsky)
Newsgroups: comp.windows.x
Subject: Re: XtAddWorkProc Question?
Message-ID: <9106031342.AA08364@maui.coral.com>
Date: 3 Jun 91 13:42:13 GMT
References: <567@math.camelot.DUPONTEOP.COM>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 27



) 
) Help, I am attempting to integrate X and Motif with a third party object 
) oriented graphics package.  I need the GUI process to check the IPC queue
) periodically and I was planning to use XtAddWorkProc (or XtAppAddWorkProc)
) to add a process to do just that.  My problem is this third party o. o.
. . .
) asked the o. o. graphics vendor and they do not know.  They suggested I use
) XtAddTimeOut instead.  I could, but I would prefer to avoid the overhead of
) setting a new TimeOut at the end of the function call.

My experience with XtAddWorkProc was that the workproc was called
continuously whenever the process was otherwise idle, using 100% of
the cpu at all times.  This doesn't slow down the process it's in, but
it does slow down other processes.  We switched to a timeout.



 Coral
     * **	Tom Tulinsky                508 460-6010
  *  **		Coral Network Corporation   fax 508 481-6258
*  ** 		734 Forest St               net: tomt@coral.com
 ***		   Marlboro, MA 01752		
  **		   U S A
*********	   Overheard in a BART station:
NETWORKS	      "I was the only NORM there!"