Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!orion.oac.uci.edu!ucivax!jchoi
From: jchoi@ics.uci.edu (John Choi)
Newsgroups: comp.sys.mac.programmer
Subject: Strange results from using TimeMgr with THINK C
Message-ID: <27A8A3C4.8227@ics.uci.edu>
Date: 31 Jan 91 23:09:56 GMT
Reply-To: jchoi@ics.uci.edu (John Choi)
Distribution: usa
Organization: UC Irvine Department of ICS
Lines: 20


    Is there a bug with the TimeMgr in THINK 4.02 or am I missing something?
I set up a TMTask, inserted the task, and tried to access the tmCount in
a while loop to monitor the count down procedure.  Inside the loop I put
in a TickCount() call to compare the two values.  The TickCount works fine,
returning a long int corresponding to 1/60 sec.  The tm.Count gives me back
a long int which doesn't seem to correspond to much - least of all 1 msec.
The units seem to be something like .4884 msec.  But the real problem I can't
figure out is why the tm.Count variable only gets updated every 4096 units or
about 4 ticks.

    Has anyone tried to use the Time Manager with THINK C?  If you have
any suggestions please help.


    I'd like to thank Landon and Russ of Apple Inc. and Russ for guiding
me to TimeMgr and an article containing the sample code that I'm tring to
run with THINK C on a Mac II.  If only I had a brain ...

Thanks,  John Choi (jchoi@ics.uci.edu)