Path: utzoo!attcan!uunet!lll-winken!ames!hc!pprg.unm.edu!unmvax!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!uw-beaver!cornell!rochester!pt.cs.cmu.edu!andrew.cmu.edu!wn0e+
From: wn0e+@andrew.cmu.edu (William Nichols)
Newsgroups: comp.sys.amiga.tech
Subject: Re:mouse interrupt
Message-ID: <wXrAh4y00V4EQ5fUsB@andrew.cmu.edu>
Date: 24 Jan 89 19:15:16 GMT
Organization: Carnegie Mellon, Pittsburgh, PA
Lines: 15

I have found from the exec manual that if I tell the mouse port to "wait", the
process will go to sleep untill there is an input to the mouse port.  This is
just fine, since I do not have to constantly poll the mouse port and use up
valuable time.  I have a problem with the Timestamp.however  I would like to
know the real time of the mouse signal, or the real time since the last
signal,but the numbers I get back are meaningless.(the seconds are garbage, and
the microseconds are always 0).
I am reluctant to make a separate function call because I would like timing on
the order of miliseconds.Could anyone point me in the right direction for
getting a time associated with a mouse signal?  Can it be done?

Thanks.

WRN
CMU Dept. of Physics