home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.aux
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!usenet.coe.montana.edu!news.u.washington.edu!uw-beaver!newsfeed.rice.edu!rice!fullmer
- From: fullmer@is.rice.edu (Robert Fullmer)
- Subject: Re: A/UX Problems
- In-Reply-To: calvinc@hawking.berkeley.edu's message of 13 Dec 1992 02:03:41 GMT
- Message-ID: <FULLMER.92Dec15111150@brazos.is.rice.edu>
- Sender: news@rice.edu (News)
- Organization: The Bavarian Illuminati
- References: <1ge5ltINN5pf@agate.berkeley.edu>
- Date: Tue, 15 Dec 1992 17:11:50 GMT
- Return-Receipt-To: fullmer@rice.edu
- Lines: 19
-
- In article <mumble> calvinc@hawking.berkeley.edu (Calvin Cheng) writes:
-
- ] The CommandShell only respond to a keyboard event only after another
- ] input event has been sent (like another key press or a mouse click).
- ] So if I type the character 'a', it doesn't show up until I've pressed
- ] a second key or click on the mouse. Output to the window is also
- ] similarly affected: output comes out a few lines at a time and then
- ] mysteriously pauses until I click the mouse or press a key.
-
- ] I have Super Boomerang and SuperClock running on a Mac IIci w/8MB RAM
- ] in addition to QuickTime.
-
- I have heard that QuickKeys and Super Boomerang both cause this problem.
- When it happened to me, the culprit was AutoIdle. Perhaps at some point
- there will be a comprehensive list of programs that cause this problem.
-
- ] Calvin Cheng
-
- Rob Fullmer : celine@athena.mit.edu : celine@rice.edu
-