Path: utzoo!attcan!uunet!ginosko!gem.mps.ohio-state.edu!csd4.csd.uwm.edu!mailrus!ncar!ames!sgi!arisia!janssen@holmes
From: janssen@holmes (Bill Janssen)
Newsgroups: comp.windows.x
Subject: Re: Handling expose events.
Message-ID: <2631@arisia.Xerox.COM>
Date: 25 Aug 89 03:19:51 GMT
References: <2623@arisia.Xerox.COM> <8908241149.AA02743@expire.lcs.mit.edu>
Sender: news@arisia.Xerox.COM
Reply-To: janssen@holmes (Bill Janssen)
Organization: PARC.Xerox.COM
Lines: 17
In-reply-to: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)

In article <8908241149.AA02743@expire.lcs.mit.edu>, rws@EXPO (Bob Scheifler) writes:
>...  If your application
>is retaining all of the necessary data on the client side in some structured
>(and hopefully higher-level) form, then regenerating the image from that data
>is often a much better solution.

I believe the statement of the problem specified that the data was not
kept by the client, but was written in sporadic bursts to the window
system...  Though the possibility of modifying the client to keep a
display list should not be discarded out of hand.

Bill

--
 Bill Janssen        janssen.pa@xerox.com      (415) 494-4763
 Xerox Palo Alto Research Center
 3333 Coyote Hill Road, Palo Alto, California   94304