Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ll-xn!mit-eddie!uw-beaver!tektronix!reed!omsi
From: omsi@reed.UUCP (OMSI)
Newsgroups: comp.sys.atari.st
Subject: Re: Changing the Mouse Handler
Message-ID: <5597@reed.UUCP>
Date: Thu, 5-Mar-87 11:28:55 EST
Article-I.D.: reed.5597
Posted: Thu Mar  5 11:28:55 1987
Date-Received: Sun, 8-Mar-87 00:54:47 EST
References: <1987Mar4.192611.666@gpu.utcs.toronto.edu>
Reply-To: omsi@reed.UUCP (OMSI)
Distribution: na
Organization: Reed College, Portland, OR
Lines: 21

In article <1987Mar4.192611.666@gpu.utcs.toronto.edu> pete@gpu.utcs.toronto.edu (Peter Santangeli) writes:
...
>	When using a Macintosh, One has the option of changing the mouses
>characteristics. Specifically, one can choose whether it moves in one to
>one correspondence with movement of the mouse, or whether the pointer moves
>faster with increased speed (logarithmically).
>	My question is this: Would it be possible to change the STs handling
>of the mouse using the VDI calls vex_motv or vex_curv? I want to change the
>characteristic for ALL programs, not just the current one. Obviously this
>would only work if the changes lived on after the program was exited (as in
>changing the keyboard map). Does this get reset after program exit?

In the outline processor Max Think, they have a desk accessory that is a
mouse 'accelerator'.  It allows you to set up the point at which the mouse
pops into a 'faster' mode.  For example, you set the threshold to 7 and the
move to 10, then if you move the mouse more then 7 pixels per mouse scan,
it will move 10 for every 7 you would mormally move.  Unfortunatly, I don't
think the accessory is public domain.

- Russ
  ...!tektronix!reed!omsi