home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pmafire!news.dell.com!natinst.com!cs.utexas.edu!zaphod.mps.ohio-state.edu!rpi!bu.edu!dartvax!Eric.J.Baumgartner
- From: Eric.J.Baumgartner@dartmouth.edu (Eric J. Baumgartner)
- Newsgroups: comp.sys.mac.hypercard
- Subject: Re: WAIT Command
- Message-ID: <1992Jul24.152649.11106@dartvax.dartmouth.edu>
- Date: 24 Jul 92 15:26:49 GMT
- References: <BrutHG.1M3@usenet.ucs.indiana.edu>
- <1682DF168.EIVERSO@cms.cc.wayne.edu>
- Sender: news@dartvax.dartmouth.edu (The News Manager)
- Organization: Dartmouth College, Hanover, NH
- Lines: 21
-
- In article <1682DF168.EIVERSO@cms.cc.wayne.edu>
- EIVERSO@cms.cc.wayne.edu writes:
-
- > No, but if you just want to create a wait state, try executing a function
- > or something. You, know: do some busy-work.
- >
- > You can roughly calculate the time spent by running this test:
- > get the ticks,
- > repeat the busy-work several times,
- > get the ticks - it,
- > divide it by the number of repeats
-
- This method is totally dependent on the machine you're running it on,
- as well as what sort of background processes might be stealing time
- from you. If you really need millisecond timing you'll have to write or
- find an XCMD.
-
- Eric Baumgartner * ebaum@dartmouth.edu
- Interactive Media Lab * - When in danger or in doubt,
- Dartmouth Medical School * run in circles, scream and
- shout.
-