On Wed, 12 Nov 1997, Colin Wood wrote:

> Dave Huang wrote:
> > 
> > On an ADB-related, but non-hwdirect-related note, yesterday, I stopped by
> > the (relatively) new Fry's Electronics in Arlington, TX... wow, that place
> > is like the hugest electronics store I've seen :) Although it didn't seem
> > as cool as the ones I've heard about in California... no weird old
> > electronics junk, and I didn't see any Jolt Cola either :) Anyways, I
> > couldn't resist getting a Mouse Systems A3 trackball... X is awful with
> > just one button :) It's working just great, but this seems a bit strange
> > to me: 
> > 
> > adb: extended keyboard at 15
> > adb: Mouse Systems A3 mouse, default parameters at 3
> > adb: standard keyboard at 2
> > 
> > What's this standard keyboard at 2 stuff about? I only have one keyboard
> > hooked up, an extended keyboard II. The same devices show up with a
> > MRG_ADB kernel. 
> 
> This is a result of the fact that the A3 mouse fakes a keyboard in
> addition to the mouse b/c by default it sends arrow keys for the 2nd and
> 3rd buttons.  I didn't realize that there may be a way to recognize it for
> what it is and ignore it when I added the support the for A3 mouse.  If I
> ever manage to get my A3 mouse fixed, I'll take care of this.
>  
> > And is the -a switch the only way to make the mouse pointer faster in X?
> > It takes about 5 half-rotations of the trackball to move the pointer from
> > the left edge to the right edge (1024x768 screen). The A3 box claims 680
> > dpr resolution (dots per rotation?), so it should be able to move faster :)
> 
> If you want, you can compile your own kernel and make it go faster :-)  I
> think that changing the device handler id to 6 instead of 3 will double
> the current resolution.  You might want to grab a copy of ADB Parser and
> play with it on the Mac side, first, tho.  When I was figuring out how the
> mouse worked, I think that I found the pattern in the device handlers it
> recognized.  Something like even-numbered device handlers were 2x normal
> resolution (I wouldn't use 4, tho, since that's the extended mouse
> address).
> 

ummmmmm... Or you could put
xset m 10 4
in your ~/.xinitrc
That works for me, I've only got 640x480 tho :( 
the first value controls how many times the mouse is accelarated, the
second value is how many pixels the mouse has to travel in a short time
for it to be accelarated.

hope that's what you were asking...
or at least will do

-Adrian