So i recently downloaded BetterTouchTool but deleted it afterwards. During the time i had it i binded the keys (Space – w) to my mouse button 4 and some other stuff to other keys. After deleting BetterTouchTool all my other bindings have disappeared except for my mouse button 4. It is still stuck on Space W.
Please help it is a pain not being able to use it. I've tried my brothers mouse and its the same thing. His mouse button 4 is still recognised as space 2. It's like my laptop somehow recognises this button as Space w now even after deleting the original app. Even when setting the button into a game it is now not recognised as mouse button 4 or 3, it is now shown as ⌘[. Is there anything that i can do such as resetting my mouse options or like how my laptop recognises this one button?
Please help Thanks you
Best Answer
There is a native keymapping tool within OS X itself in
System Preferences > Keyboard > Shortcuts tab
. There is a slight possibility that the change was made there, and you can change it manually.The more-likely issue is that the software was not uninstalled completely when removed from your Applications directory. Lots of software nowadays comes included with uninstallers that you must run to remove stuff that gets distributed all over your filesystem (which is similar, yet not nearly as bad as the whole Windows Registry/AppData situation), yet I see this type of thing becoming more complex with each new version of OS X.
There is probably a .plist file out there somewhere that is getting loaded on startup or login that is controlling this unwanted behavior. Personally, I would go about resolving this in 1 of the following 3 ways:
~/Library/LaunchAgents
or~/Library/LaunchDaemons
, etc. Sometimes they are hard to find and oddly-named. First I would do a search forcom.[better.touch.something.or.other].plist
, but many times they follow the naming convention of the company or developer, which you may also try.If all else fails, just
sudo -s
, start at/
and start executing find commands (or better yet, in all of your Libraries -- if you are unlike me and remember where all of them are):or maybe a better/faster way would be...
...and see if anything stands out. If so, make a backup just in case you are mistaken, and then delete that sucker: