Bob Arning  <arning at charm.net> wrote:
> On Sat, 2 Nov 2002 14:48:38 -0500 Lex Spoon <lex at cc.gatech.edu> wrote:
> >PS -- kudos for whoever added #addDeferredUIMessage: !  This ability is
> >needed when there is threaded code.  On the other hand, I don't get why
> >it's called what it is....
> 
> Umm, well, because it is a message whose execution is deferred until the UI thread is running.
> 

It doesn't look like a message to me.  It's neither a UI message ("error
153 has occured; meltdown is immanent"), nor an OO message ("addMorph:
with an argument of <a morph>").  It's a block.

Maybe #evaluateInUIThread: or #deferUntilUIActive: or somesuch would be
clearer.  -Lex