Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!umich!caen.engin.umich.edu!srvr1!kleinow
From: kleinow@caen.engin.umich.edu (leonard kleinow)
Newsgroups: comp.sys.mac.programmer
Subject: Serial interface replacement for mouse
Message-ID: <1990Mar19.001639.28530@caen.engin.umich.edu>
Date: 19 Mar 90 00:16:00 GMT
Sender: news@caen.engin.umich.edu (CAEN UseNet Administrator)
Organization: The University of Michigan, Ann Arbor
Lines: 23

Here's a tricky one.  I have a pointing device (a glove) that sends about
a dozen bytes of data through its serial port to the mac indicating its
position in space and the positions of its fingers.  I want to be able to
move the cursor with this and use one of its fingers as the mouse button.
I wrote a program to get the data from the modem port, and stuff the
x and y positions in the low-memory cursor positions.  If I call this 
before WaitNextEvent each time through my main loop, the cursor does in
fact follow the glove around quite nicely.  (The routine SetMouse appeared
here some time ago.)
 
This is inadequate, however.  In order to be useful, I have to be able
to select from menus, hit buttons, etc.  Things like ModalDialog, GrowWindow,
TrackControl, MenuSelect, etc., all need "fixing".  Fight now, I have to
point the glove at the menubar, then press the mouse button and use the
mouse to select!
 
This will require some patch to the system, I think.  Is there some 
place these above-mentioned traps have in common I can patch?  Has
anyone done this already?
 
Thank you,
Leonard Kleinow
kleinow@caen.engin.umich.edu