Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!rpi!uupsi!rodan!isr
From: isr@rodan.acs.syr.edu ( ISR group account)
Newsgroups: comp.sys.mac
Subject: Re: Help! Anyone know how to force the mouse to a location?
Message-ID: <3705@rodan.acs.syr.edu>
Date: 12 Jun 90 18:59:38 GMT
References: <1990Jun5.091419.14219@portia.Stanford.EDU> <16995@phoenix.Princeton.EDU> <1990Jun6.083741.4740@canon.co.uk> <3668@rodan.acs.syr.edu> <17078@phoenix.Princeton.EDU>
Reply-To: isr@rodan.acs.syr.edu (Michael S. Schechter - ISR group account)
Organization: Syracuse University, Syracuse, NY
Lines: 32





 bskendig@phoenix.Princeton.EDU (Brian Kendig) writes:
>A program doesn't have to know -- and, actually, shouldn't know --
>what input device the user is using.  Absolute devices such as
>graphics tablets typically have the interface in hardware; they move
>from place to place by simulating a corresponding sudden mouse
>movement.

Ah, but this particular digitizer communicated via the serial
port and gave it's output in the form  +/-NNN.NNN +/-NNN.NNNB

it would have been quite a project to build a hardware interface
for it as opposed to simply writing a D/A that would accept the
serial input and control the cursor.

And no, we could not buy an off-the-shelf tablet - it had to be
a sonic digitizer. In this case, at that time, moving the mouse pointer was
the only way (short of building the above mentioned inerface)
to accomplish what we needed.

In any case, this discussion started out (I believe) by someone saying
that Apple SHOULD have provided the capability - I say he/she was
right - there should be system calls, perhaps with strong warnings about
how it doesn't follow HI guidelines, but the capability should be there.


-- 
Mike Schechter, Computer Engineer,Institute Sensory Research, Syracuse Univ.
InterNet: isr@rodan.acs.syr.edu   Bitnet: SENSORY@SUNRISE