Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!news.cs.indiana.edu!att!emory!gatech!rutgers!cbmvax!peter
From: peter@cbmvax.commodore.com (Peter Cherna)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Interupts?  Help
Message-ID: <16674@cbmvax.commodore.com>
Date: 19 Dec 90 16:39:08 GMT
References: <1990Dec19.101704.4071@marlin.jcu.edu.au>
Reply-To: peter@cbmvax.commodore.com (Peter Cherna)
Organization: Commodore, West Chester, PA
Lines: 24

In article <1990Dec19.101704.4071@marlin.jcu.edu.au> glmwc@marlin.jcu.edu.au (Matt Crowd) writes:
>
>Wait! I have another idea!  How about using WaitTOF!  After
>each of these I could check the mouse event and increment the timer...
>Sound ok?

You could use timer.device to give you a poke after 5 seconds.  Then
you could Wait() on signals from both timer and intuition.

Using WaitTOF() would be like a semi-busy loop.  While you're relinquishing
cycles you don't need, you're still waking up very often though nothing
may have happened.  You can use INTUITICKS messages instead of WaitTOF().
INTUITICKS wake you up about 10 times a second, compared to 50 or 60
for WaitTOF().  But the timer.device would be the most multitasking-friendly.
In your case, INTUITICKS will likely cause no difficulties.

>Matt Crowd       Amiga Man

     Peter
--
     Peter Cherna, Software Engineer, Commodore-Amiga, Inc.
     {uunet|rutgers}!cbmvax!peter    peter@cbmvax.commodore.com
My opinions do not necessarily represent the opinions of my employer.
"Oh, PIN-compatible!  I thought you wanted me to make it IN-compatible!"