Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!mips!pacbell.com!pacbell!att!dptg!pegasus!eby
From: eby@pegasus.ATT.COM (Robert P. Eby)
Newsgroups: comp.sys.mac.apps
Subject: Re: SuperClock 3.9 Problem
Message-ID: <4955@pegasus.ATT.COM>
Date: 5 Aug 90 11:40:27 GMT
References: <HAIRSTON.90Jul30192800@henry.ece.cmu.edu> <5260@mace.cc.purdue.edu>
Reply-To: eby@pegasus.ATT.COM (Robert P. Eby)
Distribution: na
Organization: AT&T Bell Labs NJ USA
Lines: 15

In article <5260@mace.cc.purdue.edu> du4@mace.cc.purdue.edu (Ted Goldstein)
writes:
>There was one major (for me anyway) incompatability problem in 3.8 that
>I was hoping was fixed in 3.9, but I found out is still there. When typing
>in MS Word 4.0 the clock only updates as keystrokes are made. When you stop
>typing, the clock stops, when you hit a key again, the clock jumps to the
>correct time.

This may be a problem with MS Word 4.0.  If the foreground app doesn't give
SuperClock any cycles, then SuperClock can't update the clock.  I've seen
the same problem with AppMaker, but most other applications seem to
cooperate.

Robert P. Eby			UUCP:   att!pegasus!eby
AT&T Bell Laboratories		Domain: eby@pegasus.ATT.COM