Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!decwrl!pa.dec.com!wsl.dec.com!klee
From: klee@wsl.dec.com (Ken Lee)
Newsgroups: comp.windows.x
Subject: Re: XFlush/XSync inside the widget or in the app
Message-ID: <1991Feb14.103945@wsl.dec.com>
Date: 14 Feb 91 18:39:45 GMT
References: <1991Feb13.225240.547@thyme.jpl.nasa.gov>
Sender: news@pa.dec.com (News)
Reply-To: klee@wsl.dec.com
Organization: DEC Western Software Laboratory
Lines: 17

In article <1991Feb13.225240.547@thyme.jpl.nasa.gov>, kaleb@thyme.jpl.nasa.gov (Kaleb Keithley) writes:
|> Philosophically speaking, if the widgets we are writing do lots
|> of Xlib stuff (XDrawLine, XDrawImageString etc.) where is it appropriate 
|> to do an XFlush or an XSync?  Within the widget internals?  Or out in
|> the application? 

I don't know about philosophically, but practically speaking, the
application is not likely to have enough information to manage this.
In most cases, if control gets back to the application, a flush has
probably happened automatically, anyway.  If you really have to flush,
the widget's expose procedure is probably the only useful place to do it.

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