Is this a bug? [was Re: Morph>>changed should call super
changed?]
Lex Spoon
lex at lexspoon.org
Tue May 22 16:10:40 UTC 2007
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.
>
> As far as I can tell, this is a bug. The fix is trivial, so I can
> report it on Mantis, along with a little changeset with the fix.
>
> But if I did this, would anything happen? No-one seems bothered about
> this issue ...
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
More information about the Squeak-dev
mailing list
|