Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!lll-winken!ames!ucsd!hub.ucsb.edu!ucsbuxa!6500rgls
From: 6500rgls@ucsbuxa.ucsb.edu (Randall S Geels)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Strange results from using TimeMgr with THINK C
Message-ID: <8781@hub.ucsb.edu>
Date: 3 Feb 91 08:45:07 GMT
References: <27A8A3C4.8227@ics.uci.edu> <1991Feb1.182206.2880@waikato.ac.nz> <27A9AF2D.4475@ics.uci.edu>
Sender: news@hub.ucsb.edu
Distribution: usa
Lines: 11


>tmCount gets set to 10 seconds, but in units of micro seconds,
>not milli seconds.  In addition, it is a negative value

I read somewhere that the new Time Manager can be passed a value in
microseconds by calling PrimeTime() with count a negative number.
Whenever the Time Manager gets a negative number in this fasion it
interprets it as representing the delay in microseconds. Thus it makes
sense that it would use this format internally as well.

Randy Geels