Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ogicse!milton!iho From: iho@cac.washington.edu (Il Oh) Newsgroups: comp.sys.atari.st Subject: Re: STacy review in EM Message-ID: <15508@milton.u.washington.edu> Date: 31 Jan 91 01:58:47 GMT References: <1991Jan29.110121.10806@actrix.gen.nz> <1991Jan29.233400.28092@rice.edu> <40711@ucbvax.BERKELEY.EDU> <1991Jan30.203650.28@tamar.compserv.utas.edu.au> Sender: news@milton.u.washington.edu Reply-To: iho@akbar.UUCP (Il Oh) Organization: University of Washington, Seattle Lines: 29 tgray@pieman.compserv.utas.edu.au (Tony Gray) writes: > emerson@gandalf.Berkeley.EDU (Emerson Mei) writes: [text regarding the poor grade GEM got deleted] >>Sorry I couldn't quote the magazine directly. > >What the reviewer was probably referring to (without realising it) is the >way GEM handles a double-click. The first time you click the mouse, GEM >waits a preset period of time (as set in the mouse double-click speed, in >the control panel) to decide whether you will make a double-click. If >you haven't pressed the button again within the time frame, a single-click >event is posted - if you have, it is posted as a double-click. This is >quite different to the way the Mac OS (for instance) handles a double >click. With the Mac, a click posts a select event immediately. If >a second click is made within the double-click period, a second, double >click event is posted. GEM has more serious problems than that with its double click. My father, who is 60 years old and has unsteady hands, can't double click on his 1040 if his life depended on it. I think GEM doesn't recognize a double click if the mouse is moved between the clicks, even if they occured within the required timespan. I've never seen anyone have problems double clicking on the Mac. -- "And now, adding color | Il Hwan Oh a group of anonymous, Latin-American | University of Washington, Tacoma meat-packing glitterati" | iho@cac.washington.edu -- Pink Floyd, Final Cut |