AutoHotkey Community

[Peepsalot]

I have a Logitech MX 1000 mouse that has about 10 different buttons on it.
I refuse to use Logitech's drivers, and have opted to use AutoHotkey to configure these buttons.
Without the drivers, AutoHotkey is able to detect all the buttons except for 3 of them. There is an Application Switcher button, an then the mouse wheel has a side to side tilt feature for horizontal scrolling. When these buttons are presssed, even with keybd hook and mouse hook installed, no key events are displayed.
Does anyone know of a simple utility or alternative driver or something that would allow me to catch these buttons?

[TheLeO]

10 buttons you say?
sounds like its worth getting that mouse...

soz back to your problem.
why don't u install the driver and re-map it?
cuz it worked with my 7 ex-button mouse
_________________
::
I Have Spoken
::

[Peepsalot]

The drivers are crap bloatware(~36Mb), and since the mouse and keyboard drivers are a package deal, it would break the functionality of my keyboard at the same time. Everytime I press Alt-F4 it would open powerpoint, instead of the standard of closing a window like every other keyboard has done for over 10 years. Like I said, I refuse to install that on my computer.
Fool me once, shame on you. Fool me twice, shame on me.

I was hoping maybe there was some generic or open source sort of drivers that would be capable of recognizing my mouse clicks without all the extra retardedness. It's not really that big of a deal, I can live without side scrolling and a redundant Alt-Tab button, I just thought it would be neat. Hmm, guess it's time for me to learn how to write my own hardware drivers, lol.

[Peepsalot]

Yeah the buttons, in case you are wondering are as follows:
Left button
Right Button
Middle Button(scroll wheel click)
Wheel Up
Wheel Down
Wheel tilt left*
Wheel tilt right*
"Forward"
"Back"
Application switcher*
"Cruise control" up
"Cruise control" down

So technically there are twelve different button functions total.

The asterisk are the only ones that do not function. The "cruise control" are what logitech calls the buttons above and below the scroll wheel, with double arrows on them

[tinaa]

I've got the same mouse but I have the setpoint driver installed. It doesn't interfere with my keyboard (but I'm not using a Logitech keyboard).

Out of curiousity, I closed the driver from the tray icon and looked at the key history. The application button and tilt wheel buttons don't register at all. However the cruise up and down buttons register as wheel up and down buttons rather than independant buttons. With the driver uninstalled, are you seeing the cruise buttons registering with different scan codes than the wheel?

Incidentally, with the setpoint driver enabled, the cruise buttons don't appear in the history window. I assume they're being intercepted and remapped by the driver at a lower level.

[TheLeO]

well sounds like its not worth getting that mouse?
_________________
::
I Have Spoken
::

[swazi]

I don't suppose there's been any action with this mouse and these buttons in the time since this thread was last active? I'd like to try this mouse as a desktop replacement to my logitech VX Revolution, but if the app switcher can't be remapped, I'd be a button short for my script purposes.

And no, uber options isn't an option. Setpoint's a pig, dressing it up just makes it a nicely dressed pig. Logitech can't write software for peanuts...


cheers,
swazi

[swazi]

Considering the lack of answers here, I'm thinking I'll instead get myself the logitech mx620. it seems to be more or less the desktop equivalent of the VX Revolution I'm already using. Effectively the same number of buttons, etc...


cheers,
swazi

[tinaa]

I don't know about the VX revolution (I haven't used one, although Logitech is sending me a MX revolution to replace a defective MX1000...) but I tried the MX620 and found that the tactile feedback on the scroll wheel doesn't match the activation of the wheel buttons. That is if you press the wheel or tilt it to either side, you'll feel the click, but the action may or may not activate. You need to press or tilt it harder, past the click, to be sure it gets activated. I found that very annoying as I was never fully sure whether or not I'd activated the function. I tried 2 of them and they had the same problem. Logitech admitted this seems to be a common problem with this mouse...

Just a heads up if that matters to you. You might want to take a look at the MX610 or MX600 which are older versions with a standard scroll wheel (rather than the microgear one).

As for the MX1000 I used setpoint to map the extra buttons to F13+. You might be able to use one of the HID scripts to map the extra buttons without setpoint but I never tried it before I sent it back to Logitech. (To Logitech's credit, they agreed to replace my mouse despite the fact I couldn't find the receipt and it was probably past the warranty!)

I'm not too clear why the extra buttons on a MX620 should be any easier to capture without setpoint than on a MX1000... Personally, while the MX1000 was a nice mouse I found it a bit too large and heavy and the app switch and forward buttons were generally too far out of reach for the way I hold the mouse. I just got a Cordless Desktop Wave which comes with a RX8 mouse (I don't know if you can buy one by itself) which I really like. It's small and light and fits my hand really well. On the MX1000 I ended up mostly programming combinations using the back button as a modifier for the other buttons so the fact my new mouse has fewer buttons doesn't really bother me too much. In fact, since the forward button is now easily in reach on the other side of the mouse, it's easier to program more combinations. I tried to see if I could get the tilt wheel buttons to be recognized through the HID script rather than setpoint but they didn't show up. I'm not sure if I did it correctly...

What I'd really like is to find a way to call setpoint's horizontal scroll function programmatically from Autohotkey so I could assign the function to the scroll wheel rather than the tilt or other buttons. I find setpoint does a much better job with horizontal scroll than any of the methods posted for Autohotkey...

[swazi]

) I just paid for a refurbished MX620 about 2 hours ago... )

I'm quite happy with the microgear wheel on my VX Revolution; if they behave the same, I'll be happy. If they don't, well, oops. I'm assuming I'll be able to use my scripts written for the VX, as they only use XButtons 1 & 2 in combination with Left, Right and Ctrl. The tilt wheel isn't a big deal for me, autocad doesn't have scrollbars anyway. :O)

The main reason I need to get another mouse is because the VX is just that little bit too small and light for my big mitts on a daily basis, plus it belongs with my laptop, which i don't need at work...

I suppose if someone cares to post a ready-to-go script to address logitech wheel-tilting, I'd give it a go, but I'm not that worried about it...


cheers,
swazi

[Lexikos]

[swazi]

I'd noticed that vista thing on my searches through the forums here, but frankly, that's just not enough of a reason to upgrade to vista. Not to mention, I don't make those kind of decisions in my work environment...

:O)


cheers,
swazi