<\/p>\n<\/p>\n
It’s been a while since I wrote about uberOptions<\/a>, the excellent utility<\/a> that allows you to configure the extra mouse buttons on your Logitech mouse in just about any way you could want. Basically, uberOptions can unleash the potential of Logitech’s mice, expecially their higher-end models like the MX610, MX1000, G5\/G7 and VX and MX Revolution that have many extra buttons. <\/p>\n The uberOptions site is back up at a new URI<\/a>\n<\/div>\n While SetPoint itself has a lot of functionality, supporting multiple mice, uberOptions<\/a> manages to up the ante by allowing any button to be assigned to any function or keystroke. Furthermore, you can assign these settings on a per-application basis (application specific settings), so that buttons can perform different functions depending on which window currently focused. This is especially useful in games, where sometimes, the extra mouse buttons aren’t detected by the game itself. This can be fixed by using uberOptions to assign\/bind keystrokes to the mouse buttons just for that game – that way your mouse will still work normally outside of the game. This can make the extra buttons on your Logitech mouse very useful in games that have lots of different actions, normally assigned to keyboard commands only. The latest version of uberOptions<\/a> is stated to support SetPoint versions 2.22-3.30. I tested it out with the latest version of SetPoint<\/a>, (v. 4.00, released June 5th, 2007), and it also worked. So, it’s okay to update to v. 4.00 if it’s needed for your mouse\/keyboard to be recognized. However, you may encounter a problem if the version of SetPoint you installed didn’t include some files for the mouse you use. Your mouse will work, but instead of an actual image of your mouse being displayed in SetPoint’s configuration dialog, a greyed-out generic mouse image<\/a> will be displayed instead. In this case, uberOptions won’t work with your mouse.<\/p>\n\nUpdate – 2008-02-01<\/h3>\n
\n<\/p>\nChanges, fixes and updates<\/h3>\n