Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 UW 5/3/83; site uw-beaver
Path: utzoo!watmath!clyde!burl!ulysses!cbosgd!ihnp4!drutx!houxe!hogpc!houti!ariel!vax135!cornell!uw-beaver!info-mac
From: info-mac@uw-beaver.UUCP
Newsgroups: fa.info-mac
Subject: Update events
Message-ID: <1265@uw-beaver>
Date: Fri, 20-Jul-84 22:18:24 EDT
Article-I.D.: uw-beave.1265
Posted: Fri Jul 20 22:18:24 1984
Date-Received: Sun, 22-Jul-84 01:36:20 EDT
Sender: daemon@uw-beave
Organization: U of Washington Computer Science
Lines: 18

From: INTMET@BBNA.ARPA
It seems that the window manager does not generate an update event for the
desk top.  Since the desk top isn't realy a window it isn't clear how it
would refer to it.  A comment in the work shop pascal sources that were
included in sumacc annotates a check if the update is on a window who's
pointer is null says "Whats this for?"  And the awnser seems to be... if
it was ever decided to generate update events for the desk top then it
might be reffered to by using a null pointer in the event message.
  I presume that finder updates its "desk top" by slipping a real window
over the entire desk, sort of a table cloth I guess.  
  The manual suggests that if you recieve an update event for a desk
accessory that you ignore it, it also says that it should neve happen.
It realy isn't a good idea ever to ignore an update event, the event
manager checks for windows which need updating often, if you don't call
BeginUpdate and EndUpdate on the window once you get the update event then
the event manager will keep throwing the event at you with a passion.
			Ben Hyde
-------