Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!ut-emx!ccwf.cc.utexas.edu!awessels
From: awessels@ccwf.cc.utexas.edu (Allen Wessels)
Newsgroups: comp.sys.mac.misc
Subject: Re: Not another NeXT defector???!!!
Message-ID: <39328@ut-emx.uucp>
Date: 7 Nov 90 21:56:03 GMT
References: <1990Nov7.212457.8903@ctr.columbia.edu>
Sender: news@ut-emx.uucp
Reply-To: awessels@ccwf.cc.utexas.edu (Allen Wessels)
Organization: The University of Texas at Austin
Lines: 19

In article <1990Nov7.212457.8903@ctr.columbia.edu> eboltz@jhuvms.hcf.jhu.edu (Eric S. Boltz) writes:

>One reason the mac's gui is fast is because when you click the mouse 
>EVERYTHING STOPS and the cpu only listens to the mouse. On the NeXT it not
>only continues to run other programs but continually draws the window (not
>just its outline).

I sure wish I knew how this rumor keeps spreading around.  I'm not much of a 
mac programmer, but I don't have to be to disprove the notion that the CPU stops
on a mouse click.

Just start a download in the background with MultiFinder.  Now click on a menu.
Notice that the modem receive light does not go off?  Notice that the bytes
received counter keeps incrementing?

If I recall correctly, dragging windows as an outline is an option you can 
change in the Finder.  (Either that, or I have an init that lets me drag the
window and not just the outline.  With dozens of inits, you tend to forget what
the original interface really was.)