[BUG]Morph>>updateableActionMap

Withers, Robert rwithers at quallaby.com
Mon Mar 18 20:36:22 UTC 2002


Hi Jim,

I actually didn't write this Morph code, but grabbed it from the
StableSqueak effort, IIRC, so I am not sure of the issues.  I think that the
only reason the #myEvents is used is to match the selector name used in
Object for the map?  Or is it the ivar name holding the actionMap in the
EventModel?  hmmm.

I don't think that the property name is used for anything but the handful of
methods in Morph which get and set the property.  Note that the get doesn't
set it, only adding a registration will send updatableActionMap.   If you
have a fix, then I think you are most qualified to produce it for Morph, Mr.
Zurgle.  Go for it!

Relating to your PS, I was worried that this case may present itself, but
just as quickly I forgot to post something to the list.  My apologies.  From
the sound of more recent Module discussions, there was talk about having
protocol namespaces.  Perhaps the concept of deprecation could be included
there?  Furthermore, it may be interesting to have a DeprecatedError thrown
when these methods are called, so you know what has changed.  Really
stretching here, but it could even be possible to define rewrite rules to
fix those portions of the code that call deprecated protocol.

cheers,
Rob

> -----Original Message-----
> From: Jim Benson [mailto:jb at speed.net]

> PS: It's just frustrating sometimes when things get killed, 
> exasperated this
> time by the fact that my stuff didn't work with the module 
> stuff either. Too
> many variables to solve at once. I think in the future a better way to
> handle changes to things in the base image is to post a 
> "grave marker" that
> informs that the protocol has been deprecated upon invocation 
> (even better
> if the new protocol is mentioned). A release later, the 
> deprecated protocol
> can be removed. Thanks for your work on the new framework!!!
> 



More information about the Squeak-dev mailing list