Newsgroups: comp.sys.amiga.advocacy
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!news.cs.indiana.edu!ux1.cso.uiuc.edu!news.iastate.edu!vaxf.iastate.edu!TAAB5
From: taab5@isuvax.iastate.edu (Marc Barrett)
Subject: Some WB2.0 Peeves
Message-ID: <1991Jun23.210647.20152@news.iastate.edu>
Sender: news@news.iastate.edu (USENET News System)
Reply-To: taab5@isuvax.iastate.edu
Organization: Iowa State University, Ames, IA.
Date: Sun, 23 Jun 1991 21:06:47 GMT
Lines: 22


   I do most of my computer-related work at school on DECstation 3100.  One
of the things I have noticed is that on this system, when the mouse is moved
to the top of a window and a menu is pulled down (I use DECterm, which has
menus), any motion going on in the current window does not stop.  (If a
bunch of text is scrolling, it keeps on scrolling, for instance).  Also,
if a window is moved, the program controlling that window stops, but any
animation in other windows keeps on moving.

   My question is: why can't this be so on an Amiga?  With WB2.0 (or 1.3
or whatever), when you pull down a menu or drag a menu or icon or whatever,
all animation in motion on the current screen stops.  I guess I don't quite
understand why this has to be on a computer with such awesome animation as
an Amiga.  

  -------------------------------------------------------------
 / Marc Barrett  -MB- | BITNET:   XGR39@ISUVAX.BITNET        /   
/  ISU COM S Student  | Internet: XGR39@CCVAX.IASTATE.EDU   /      
------------------------------------------------------------    
\        The great thing about standards is that          /
 \       there are so many of them to choose from.       /
  -------------------------------------------------------