Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!romp!d75!root
From: root@johnbob.uucp (/4194303)
Newsgroups: comp.windows.x
Subject: Re: Problem with writing in the window
Message-ID: <2613@d75.UUCP>
Date: 3 Sep 89 21:08:13 GMT
References: <3239@wasatch.utah.edu> <1752@bacchus.dec.com> <418@stretch.MUN.EDU>
Sender: news@d75.UUCP
Reply-To: root@reed.UUCP (/4194303)
Organization: Austin, TX
Lines: 31

In article <418@stretch.MUN.EDU> jeff1@stretch.mun.edu (Jeff Sparkes) writes:
>In article <1752@bacchus.dec.com> klee@gilroy.pa.dec.com (Ken Lee) writes:
>   In article <3239@wasatch.utah.edu>, margaret%muav.utah.edu@wasatch.utah.edu (Malgorzata Sturgill) writes:
>   > ...as long as there is no window managerrunning ...
>   ...Most X
>   programs wait for an Expose or Map event before drawing.  Many...
>...One would give
>both events, but only after the second one could you draw.  The other
>gave you only one event, and it was the opposite.  i.e. you had to
>wait for an expose with one, and a map for the other.  I guess (hope) this
>will be solved by ICCCM window managers.

I think you should only have to redraw for an Expose event.  Some window
managers will re-parent your window and map it, but the parent window
will be unmapped and you don't get an expose event.  In any case if your
window is unmapped you shouldn't get any expose events from it, and if
any part of it becomes visible you should get an Expose event.  I don't
think the type of window manager (ICCCM or not (or none)) will change
this (bug/feature) of X.

Also, there are situations where multiple expose events and window
resizing can cause unexpected output when there are long network delays.
You might consider clearing the exposed area before redrawing it when
you get an expose event.  This is also a (bug/feature) of X.


..!uunet!cs.utexas.edu!ibmaus!auschs!johnbob.austin.ibm.com!root
							    !john
John Harvey						    !johnbob
I don't speak for anybody.  Not even myself.
Please forgive my employers.  They know not what I do.