Mouse Buttons- should KDE provide a GUI to "fix" faulty button numbers?

[Jeffery MacEachern]

On Fri, Feb 4, 2011 at 16:14, Aaron J. Seigo <aseigo at kde.org> wrote:
> On Friday, February 4, 2011, Rick Stockton wrote:
>> Background for my question:
>>
>> Different mice, even different mice from the SAME manufacturer,
>> sometimes emit different X11 Button numbers for the same button. For
>> example, the tilt wheel on Logitech's V220 emits Button6 for "Scroll
>> Left" and Button7 for "Scroll Right" -- while Logitech's LX6 emits
>> Button11 for "Left" and Button12 for "Right".
>
> is it possible to identify these mice (or at least some/most of them) when
> they are plugged in? if so, could we then build a list of "known" mice with
> configurations mapped to them for optimal defaults?

This should be simply detectable by USB IDs, shouldn't it? It would
then "just" be a matter of compiling a database of such information.

>> Should we add an enhanced Button Mapper as part of this project? My vote
>> is YES, because
>
> agreed.

+1

>> Question 2: Should we push the user-selected map down to only Qt, or all
>> the way down to X11?
>
> if possible, this would be great imho.
>
> --
> Aaron J. Seigo
> humru othro a kohnu se
> GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
>
> KDE core developer sponsored by Qt Development Frameworks
>
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel at kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
>