Message-ID: <327644A4.C7F@mail.amsinc.com>
Date: Tue, 29 Oct 1996 12:53:40 -0500
From: Joel Nylund <joel_nylund@mail.amsinc.com>
X-Mailer: Mozilla 3.0Gold (WinNT; I)
MIME-Version: 1.0
Newsgroups: comp.lang.smalltalk
To: gmecchia@cc.colorado.edu
Subject: Re: [VW] about onChangeSend:to:
References: <550cg9$5uf@lace.colorado.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: jnylund.amsinc.com
Lines: 26
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornellcs!newsstand.cit.cornell.edu!portc01.blue.aol.com!news-peer.gsl.net!news.gsl.net!news.mathworks.com!uunet!in2.uu.net!dns.amsinc.com!

gmecchia@cc.colorado.edu wrote:
> 
> Hello,
> 
> can the VisualWorks historians tell me why onChangeSend:to: was
> not expanded to something like onChangeSend:to:with: so that an
> "event argument" can be provided with the message sent being a
> keyword message?
> 
> The fact that only onChangeSend:to: is available implies that
> only unary messages are sent, and the receiving object is almost
> always the sender ("self") because it only can know about how to
> get the value of the value model that changed (since it is usually
> an instance variable in that object).
> 
> Alexis Rzewski
> gmecchia@cc.colorado.edu


It sounds like you want dependencies,

you can send multiple parameters when a change occures using
update: with:
or 
update: with: with:
or
update: with: with: from:

-Joel
