> From: "Lex Spoon" <lex at cc.gatech.edu>
> In Morphic, they're actually already gone.  That's why you can  
scroll a text pane
> and have your BouncingAtomsMorph keep bouncing around while you do  
it.  Of
> course, the logic for menus and for text highlighting and things  
like that, which
> take a long time to execute, are made more complicated because  
they have to store
> intermediate states in instance variables--the extra interactivity  
is not for
> free.

Wouldn't that added complexity go away if an asynchronous  
message/event delivery model were used so that these tasks could be  
coded as plain methods that wait for messages to arrive?

Marcel