Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!umich!sharkey!msuinfo!convex.cl.msu.edu!jap
From: jap@convex.cl.msu.edu (Joe Porkka)
Newsgroups: comp.sys.amiga.tech
Subject: Re: INTUITICKS Problem!
Message-ID: <1990Dec18.063853.13668@msuinfo.cl.msu.edu>
Date: 18 Dec 90 06:38:53 GMT
References: <1990Dec17.220906.15730@hoss.unl.edu>
Sender: news@msuinfo.cl.msu.edu
Organization: Michigan State University
Lines: 18

252u3130@fergvax.unl.edu (Phil Dietz) writes:

>I'm writing a program that does a BUNCH of calulations (3d ray trace
>stuff).  Well as it turns out, if I put the calculation part of the
>program in a CASE INTUITICKS: loop, it runs 10% faster than if I just
>let it run (and not be multi-tasking happy!) Weird....
Hmm, not sure. Care to give more details? How do you decide how much
calculation per intuitick? how were you doing it without intuiticks?
> 
>Now the problem is, if I use the INTUITICKS trap, the WINDOW ALWAYS HAS
>TO BE SELECTED!!  If the window isn't selected it just hangs at the spot
>until I re-activate it.  Whats going on?  Is there a way around it?  

INTUITICKS only happen in the active window.
You can get input.device ticks, which are the ultimate source
on intuiticks, by adding yourself as an input hanlder. 
NOTE: do as little as possible in an input-handler, else you can
mess things up by slowing things down.