Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!oitnews.harvard.edu!yale!yale.edu!spool.mu.edu!howland.reston.ans.net!torn!nott!cunews!dbuck
From: dbuck@superior.carleton.ca (Dave Buck)
Subject: Re: [VW2] Detect mouse moving over a widget
X-Nntp-Posting-Host: superior.carleton.ca
Message-ID: <DFE8DF.1M4@cunews.carleton.ca>
Sender: news@cunews.carleton.ca (News Administrator)
Organization: Carleton University, Ottawa, Canada
References: <43uqv7$ake@vixen.cso.uiuc.edu> <DFC5n4.Cpn@cunews.carleton.ca> <sehyoDFDoBK.3qK@netcom.com>
Date: Sun, 24 Sep 1995 04:56:03 GMT
Lines: 32

In article <sehyoDFDoBK.3qK@netcom.com>, Sehyo Chang <sehyo@netcom.com> wrote:
>postOpenWith: aBuilder
>
>	super postOpenWidth: aBuilder.
>	aBuilder window controller: (UserAplicationStdardSystemController new).

For this to work, you have to move this from a postOpenWith: to a
postBuildWith:. By the time postOpenWith: runs, the controller has
already been scheduled and it's too late to change it.

Otherwise, this technique seems to work fine.  The controller has to
dispatch a message to the model to get it to update the status
information but this isn't a problem.

>
>pluses:	no processes to manage.
>minuses: additional classes 
>
>-- sehyo chang
>

One additional plus is that it refreshes the status info slightly
faster than the background process can.

David Buck
dbuck@ccs.carleton.ca
_________________________________
| David K. Buck                 |
| dbuck@ccs.carleton.ca         |
| The Object People             |
|_______________________________|

