Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!indri!bin
From: bin@primate.wisc.edu (Brain in Neutral)
Newsgroups: comp.sys.mac.programmer
Subject: Re: TransSkel update events
Message-ID: <175@indri.primate.wisc.edu>
Date: 31 Mar 89 18:09:24 GMT
References: <16127@dcatla.UUCP>
Sender: bin@primate.wisc.edu
Reply-To: bin@primate.wisc.edu
Lines: 22

From article <16127@dcatla.UUCP>, by dlmnm@dcatla.UUCP (Michael N. Moran):
> The problem is that TransSkel does not provide the window update
> procedure with the window pointer. I suppose it assumes the
> update procedure is associated with a particular window. For most
> events this works fine since FrontWindow can be used to get the
> window pointer. In the case where a window other than the one
> in front receives an update event, there is no way for the update
> procedure to know with which window the event is associated.

It isn't necessary, because the port is set to the window to be updated
before the update procedure associated with the window is called (and
restored afterward).  Therefore, you can get the window pointer with
GetPort().  I believe that this is documented in the manual.

By the way, you do *not* want to use FrontWindow(), because you
can get update events for windows other than the frontmost one.
Use of FW will lead you to update the wrong window under such
circumstances.

Paul DuBois
dubois@primate.wisc.edu		rhesus!dubois
bin@primate.wisc.edu		rhesus!bin