home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!umd5!mac39-pg2.umd.edu!user
- From: de19@umail.umd.edu (Dana S Emery)
- Newsgroups: comp.sys.mac.programmer
- Subject: Re: FlushEvents necessary? (was: Re: Toolbox init)
- Message-ID: <de19-200892050741@mac39-pg2.umd.edu>
- Date: 20 Aug 92 09:22:02 GMT
- References: <1992Aug11.152914.18785@uni-paderborn.de> <13992@gazette.bcm.tmc.edu> <hammett.714004576@sbsu1.aukuni.ac.nz> <jpugh-160892232829@90.20.3.200>
- Sender: news@umd5.umd.edu
- Followup-To: comp.sys.mac.programmer
- Organization: Personal
- Lines: 21
-
- If ones application interpretes key events in a way that make blind type
- ahead a dangerous option, then by all means flush away.
-
- scenario: The user mouses into a file icon file name, intending to correct
- it, but instead his mouse button stutters, and accidentally launches the
- file. Since the poor fool might have been simultaneously typing with the
- left hand, the characters typed will end up misconstrued.
-
- For most programs, this would not be any problem, but text mungers which
- retain the previous selection context (Nisus, MPW shell) would respond by
- supplanting the selected text with the type ahead. If the type ahead
- included a fat-fingered command-s, poof, instant lost data.
-
- Also, the user is now pissed at himself, and is likely to be in a
- dangerously energetic mood, where self destructive behaviour might occur,
- (ie, quit w/ reflexive save changed).
-
- Yes, virginia, in my experience since 1968, it has even happened to me.
- --
-
- Dana S Emery <de19@umail.umd.edu>
-