Dave Mason wrote:

>I reported a pretty serious bug on Mantis 5 weeks ago, but there is no
>evidence that anyone has looked at it since.  I know this is a volunteer
>effort, and I'm looking forward to the day I grok this all enough to
>contribute, but it's kind of frustrating.
>
>It's bug number 2114, and similar problems are holding me up now.  It's
>very difficult to track down problems in Morphic where #step is
>involved.  I get MessageNotUnderstood for #adaptToPoint:andSend: which
>happens because positionWhenComposed is nil... but when you go in with
>the debugger, it's happily a valid Point.
>
>Very frustrating.
>
>../Dave
>
>
>
>  
>
I looked at your Clock code and notice that you are doing stuff that are 
not very safe in Morphic.
The Clock code looks more like a MVC app.
Morphic runs in a single process and updating from another process is 
probably what causes your trouble.
Take a look at the class ClockMorph to see a morphic approach to what 
you are doing, using #step etc.
Karl