ZAxisMapping causing trouble

[Marcus Schäfer]

Hi,

> On Nov 10, 05 12:34:32 +0100, Marcus Schäfer wrote:
> > Hi,
> > 
> > > On Nov 09, 05 16:41:52 -0800, Kean Johnston wrote:
> > > > >Hmm, that's not quite how I did it on Solaris, but the Solaris mouse
> > > > >driver reports wheel events with separate event ids, not mapped to
> > > > >buttons already, so in my case it was:
> > > > I have adjusted the SCO and UnixWare ports to behave the same way,
> > > > and re-instated the default value for ZAxisMapping. May I commit
> > > > the attached patch for RC2?
> > > 
> > > With setting the default for ZAxisMapping we again hide Buttons 4-7 to
> > > the application by default. Or am I missing something?
> > > I would strongly vote for a changed default ButtonMapping (like
> > > indicated in the code).
> > > 
> > > Or am I missing some information here?
> > 
> > Matthias what ButtonMapping should I add to the SuSE configuration
> > when the default is gone ? I think we leave a gap on 4 to 5 right ?
> 
> Marcus, wait a second, as ZAxisMapping default is back to "4 5 6 7", I
> think we should change the ButtonMapping default back again as well.
> Just waiting for confirmation.
> 
> Otherwise the default with SUSE (and at least most Linux variants)
> should be "1 2 3 8 9 10 11 12 13 14 15" or something similar.
> Buttons that are not generated do not account for the number of
> available buttons, so this larger string doesn't hurt anyone.

ok, I will wait :-)

Regards
Marcus
-- 
 Public Key available
 -------------------------------------------------------
 Marcus Schäfer (Res. & Dev.)   SUSE LINUX Products GmbH
 Tel: 0911-740 53 0             Maxfeldstrasse 5
 FAX: 0911-740 53 479           D-90409 Nürnberg
 http://www.suse.de             Germany
 -------------------------------------------------------