On Tue, Jan 07, 2003 at 07:32:34PM -0800, Ned Konz wrote:
> On Tuesday 07 January 2003 06:19 pm, RossBoylan at stanfordalumni.org 
> wrote:
> > My application has a thread that ticks away and causes some updates
> > to the display.  It may be relevant that the errors are being
> > raised from that thread, rather than my main thread (the top of the
> > stack shows how it started).  [Or do I mean the bottom?
> >  Graphically it's at the end of the list below, but its the first
> > item on the stack.]
> 
> Hi Ross,
> 
> Morphic is single-threaded.
> 
> But it looks like you're invalidating Morphs from a non-UI thread.
> 
> Doing this can cause problems, as you've found.

Oh my.  That certainly clears things up, and thanks for the suggested
fixes.  They should be easy to do.

Does anyone know why Morphic is single-threaded?  I always made fun of
MS Windows for exactly this "feature", and it's kind of disappointing
to see it here.