Re: ALPS touchpad with 4 directions button doesnt work as intended

[Dmitry Torokhov <dmitry.torokhov@gmail.com>]

On Mon, Nov 02, 2009 at 07:20:26PM +0200, Maxim Levitsky wrote:
> On Sun, 2009-11-01 at 21:38 -0800, Dmitry Torokhov wrote: 
> > Hi Maxim,
> > 
> > On Sat, Oct 31, 2009 at 04:10:18AM +0200, Maxim Levitsky wrote:
> > > I have a acer 5720G laptop, and its touchpad (ALPS) has three buttons,
> > > usual left/right, and middle button that can be pressed in 4 directions.
> > > Up/down direction work fine, but left/right doesn't. This means that
> > > left direction  produces middle button click, and right direction
> > > doesn't work at all.
> > > I took a look at source, and I see that driver doesn't even know about
> > > such configuration.
> > > 
> > > Now I am sure its very easy to figure out what is send when no working
> > > button is pressed, but I am a bit confused what BTN_* event to assign to
> > > it, so it will work as horizontal scroll as intended.
> > > And unassign middle button from other direction....
> > > 
> > 
> > Synaptics driver maps multi-button to BTN_0...BTN_8 and it looks like
> > synaptics X driver maps teh 4-button case by default to
> > up/down/left/right scroll so I'd map ALPS the same.
> > 
> Thanks!
> 
> One question, should I expect some resistance because the button won't
> work as middle button by default? (I am sure that in X its easy remap it
> back)
> 

I am pretty sure these kind of buttons allow 5 distinct presses - left,
right, up, down and "straight" (which may be reported either with
distinct packet or by reporting both up/down or left/right presses) so
you don't have to loose the middle button. This is a speculation
though...

-- 
Dmitry