Looking at how other morphs handle deletion, they all do something to
themselves and then call super delete.

One thing that is now clear to me is that somewhere at the heart of this
problem is the fact that the ScorePlayer and the ScorePlayerMorph are connected
but not related. It feels like a containership hierarchy. A ScorePlayerMorph
doesn't open itself the way I did in my Workspace. It uses a method called
openOn:title: with the first argument being a ScorePlayer.

So it's back to the drawing board. My Workspace worked but wasn't good code. 
> I'm open to suggestions, though. This can't be so hard; it's in Chapter 2 of
> a
> primer, fergodsake!
> > parent class != parent morph
> > 
> > -- 
> > Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
> > <merlyn at stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
> > Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
> > See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl
> training!
> > 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Get email at your own domain with Yahoo! Mail. 
> http://personal.mail.yahoo.com/
> 


__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail. 
http://personal.mail.yahoo.com/