Coming soon - Get a detailed view of why an account is flagged as spam!
view details

This post has been de-listed

It is no longer included in search results and normal feeds (front page, hot posts, subreddit posts, etc). It remains visible only via the author's post history.

26
How is it 2016 and we still can't easily map mouse buttons?
Post Flair (click to view more posts with a particular flair)
Post Body

Yes, you can try to translate this post from archlinux , or this 4 year old Ubuntu post, both of which rely on xorg.conf files, which aren't present by default in current mint. (or at least they aren't located in /etc/X11/ or a few other locations I went to look for). And you have to be familiar and comfortable with editing config files and terminal and stuff.

What I like about Linux Mint is that it is almost as easy to use as Windows. I can, generally speaking, put it on non-technical people's computers that aren't up to running current windows versions. Terminal and config file editing only really come up if you're doing development or doing some deeper system tweaks.

Take keyboard shortcuts for example. There's a simple window in preferences to set a keyboard shortcut to do just about anything you can imagine, including launching a script that can do functionally everything you can imagine a keyboard control doing. But open up the mouse page and you get... nothing. No mouse button configuration, no mapping, no shortcuts. You can launch xev in terminal and see that the system sees all these buttons and events... there's just no interface to be able to tell the system what you want it to do when an event occurs.

It seems practically every mouse on market these days has more than the basic 3 buttons. It's entirely unreasonable that there's not an easy gui editor to control what those buttons do.

*Yes, I am aware of easystroke, but there are some problems with it. Namely that it's designed to perform gestures and not simple button mapping. It can map buttons, sure, but it isn't really designed around that feature. This specifically stands out because I prefer the thumb button pair to be cruise up/down, not forward/back. But holding in a button triggers a 'gesture' response, not a sustained click, so it only acts to press a button once (say scroll up one click).

Author
Account Strength
100%
Account Age
13 years
Verified Email
Yes
Verified Flair
No
Total Karma
75,220
Link Karma
8,163
Comment Karma
66,692
Profile updated: 2 days ago
Posts updated: 8 months ago

Subreddit

Post Details

We try to extract some basic information from the post title. This is not always successful or accurate, please use your best judgement and compare these values to the post title and body for confirmation.
Posted
8 years ago