Path: utzoo!attcan!uunet!wuarchive!decwrl!chico.pa.dec.com!klee
From: klee@chico.pa.dec.com (Ken Lee)
Newsgroups: comp.windows.x
Subject: Re: Forcing application to process events
Message-ID: <2654@bacchus.dec.com>
Date: 1 Feb 90 18:33:10 GMT
References: <9002011609.AA05640@ATHENA.MIT.EDU>
Sender: news@decwrl.dec.com
Reply-To: klee@decwrl.dec.com
Organization: DEC Western Software Laboratory
Lines: 22

In article <9002011609.AA05640@ATHENA.MIT.EDU>,
Matthew.Diamond@MAPS.CS.CMU.EDU writes:
> The problem is that these applications were not written to the event-driven
> model.  I can process events whenever my code is called (most user I/O is
> handled by me, since I am replacing keyboard procedures with code that
accepts
> input from the mouse too).  But there are times when my code is not being
> called and the application's display freezes for a while.

Two possible solutions are:

1.  Catch and dispatch events yourself, and live with non-updated
displays when you can't catch events.

2.  Create a second process to do X stuff using a normal X event loop
and communicate with the main application using sockets, pipes, or
ptys.  Examples of this method include xmh, xdbx, and even xterm.

Ken Lee
DEC Western Software Laboratory, Palo Alto, Calif.
Internet: klee@decwrl.dec.com
uucp: uunet!decwrl!klee