At 22 May 2007 18:10:40 +0200,
Lex Spoon wrote:
> 
> Simon Guest <simon.guest at tesujimath.org> writes:
> > At Tue, 15 May 2007 22:11:35 +0100,
> > Simon Guest wrote:
> > > I've created a "dependent" morph which should be updated if one of
> > > several others are changed.  So I called addDependent: on the morphs I
> > > am observing, expecting to be called back with update: via
> > > Object>>changed.
> > > 
> > > However, Morph>>changed overrides Object>>changed, and does not call
> > > super, thus stopping this from working.

> Maybe it should call super changed, I don't know.  In the meantime,
> you can of course use #changed: with an argument, insead of #changed.

Lex,

Thanks for the reply.  If I was making my own morph, I could indeed do
that.  But in my case I want to know when the handles of a
PolygonMorph are dragged around, which causes changed to be called,
but not changed:

I'll raise a bug report ...

cheers,
Simon