MadMan2k madman2k at
Thu Nov 17 13:41:57 CST 2005

sorry - the last one was hardly readable

On Do, 2005-11-17 at 09:35 +0100, Sebastien Bacher wrote:
> Le mercredi 16 novembre 2005 à 23:34 +0100, MadMan2k a écrit :
> > > doesn't look like it's a high priority the gnome folks.
> > as you can see I opened some of them - but since there was no reaction
> > from the devs I had doubts that they read it at all.
> Just a not, the maintainers usually read the bug. Those are not trivial.
> That's not clear what is required and if that's an application bug to
> me. Other point, it's likely that most of the maintainer don't have a
> such mouse and so can't play with it even if they would like.
I know that fixing it on application level is probably not the best
solution - but that's why I am asking.
Thanks to Xmodmap you can send the side button events with your
scroll wheel - so this should not be a problem...

> > Basically I want to upper the priority of this issue, so it will
> > be accepted as the default behaviour for GNOME apps.
> Is there many users having a such mouse? Are you sure that's an
> application issue?
I don't know exact numbers, but this is not only limited to the MX
series - it basically applies to any mouse with two side buttons.
And since windows supports the mouse-(forward|back) events in its
standard driver so the number should be not negligible.
Furthermore many windows apps support these events - a good example is
firefox, which supports them in its linux version as well.
Firefox is also the reason why I though of this as an application bug -
but after I have thought a bit more about it, it makes more sense fixing 
on gnome level by offering a advanced mouse configuration tool, where 
users could configure the events triggered by mousebuttons.


More information about the ubuntu-devel mailing list