Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site spuxll.UUCP Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!spuxll!ech From: ech@spuxll.UUCP (Ned Horvath) Newsgroups: fa.info-mac Subject: Re: Behaviour of InvalRect Message-ID: <594@spuxll.UUCP> Date: Tue, 18-Dec-84 16:25:12 EST Article-I.D.: spuxll.594 Posted: Tue Dec 18 16:25:12 1984 Date-Received: Thu, 20-Dec-84 02:25:57 EST References: <238@uw-beaver> Organization: AT&T Information Systems, South Plainfield NJ Lines: 20 Almost right. the paintWhite flag affects what the Window Manager does when a window gets EXPOSED as a result of a window in front of it being closed, moved to the back, or moved. I.e. the Window manager - paints the exposed area white, then - adds the exposed area to the invalid region with something that might as well be InvalRect. The other side of your problem is that TECalText and TEUpdate seem to be a bit braindamaged about the precise case you describe (I have been here!). i.e., the window gets WIDER, so there are fewer lines of text, but the no-longer-relevant stuff at the bottom stays. Yecch. Seems that in this case the ONLY option you have -- or at least, one that works -- is to use EraseRect to clear window's portRect, then invoke TEUpdate. To reiterate: paintWhite ONLY affects regions the WMgr "knows" just got exposed. =Ned=