Mouse Button Numbers are Off-Topic, and etc. (You're RIGHT, thanks)

Rick Stockton rickstockton at
Mon Feb 7 22:11:29 CET 2011

On 02/07/2011 10:48 AM, Fredrik Höglund wrote:
> On Sunday 06 February 2011, Rick Stockton wrote:
>> So, here's my tentative design: At KDE startup, do an "xinput list
>> --short" and grep for pointer device names. Then, if we ALREADY have a
>> matching [device-name] section in our config file (maybe with filename
>> "./kde/share/conf/mousebuttonconfigs.rc"), and the device is enabled,
>> execute "xinput set-button-mapping" with the values in the file stored
>> for that device. Here's an optional add-on, and my vote would be to do
>> this as well:
> First of all I want to point out that this discussion is off-topic on
> this mailing list, since the KCM's for configuring input devices have
> nothing to do with Plasma. Please move this discussion to a more
> suitable list, such a kde-core-devel.
YES, I'll join that list, and MOVE IT THERE.
Plasma 4.7 effects would be a good user of these enhanced shortcuts (per 
my previous entries, it's a big disadvantage versus the Compiz UI). But 
this SHOULDN'T be the place for discussing all the underlying baggage; 
Thanks for pointing me to the right place. :)))
> Secondly, XInput provides a list of labels for the buttons on each
> device, and Qt should use the label to determine what a particular
> button does.
> Also, please don't write frontends for command line utilities when
> there is a perfectly good library available (which the command line
> utility also uses).
> Regards,
> Fredrik
I said that "I WOULD" use command line and grep the console result (with 
vast amounts of overhead). I had MEANT to describe the process as being 
"like" doing this from the console. Bleary-eyed mistake while writing my 
entry; thank you for highlighting the error in my description.

More information about the Plasma-devel mailing list