Logitech Cordless Presenter (Bluetooth) and mysterious 4th button
Logitech Cordless Presenter (Bluetooth) and mysterious 4th button
- Subject: Logitech Cordless Presenter (Bluetooth) and mysterious 4th button
- From: email@hidden
- Date: Fri, 30 Apr 2004 12:24:05 -0700 (PDT)
Hello,
I just bought the following:
http://www.logitech.com/index.cfm/products/details/US/EN,CRID=3,CONTENTID=4981
This is a bluetooth-powered presentation mouse from Logitech. I got it to
communicate with my powerbook over built-in bluetooth with no problems.
The mouse has two modes: mouse and presenter. When in mouse mode, you
just put the thing on the desk/table and it works exactly as advertised
(though Logitech doesn't officially support Macs for this product). Left
button, right button, and the up/down scroll buttons all work great. When
you put the mouse in presenter mode (via a little button on the bottom),
you loose the mouse part, and you're supposed to get functionality for
left button, right button, and built-in laser pointer.
The problem is that in presenter mode, my right button disappears, so I
only get the left mouse button and the laser. I want to be able to
program these two buttons for back/forth in Web-based (powerpoint-like)
presentations. Since the left mouse button is still behaving, I was able
to map this button to the right-arrow key with GamePad Companion.
However, gamepad companion nor OS X (Panther), seem to be detecting the
other button. I ran the "xev" program in X11 to see if that would detect
the click, and yes, xev tells me that in presenter mode, the right mouse
button is "Button 4". By the way, in regular mouse mode, the right button
is button 3.
Gamepad Companion allows for a mapping of up to eight mouse buttons, but
I've tried them all and none seem to be grabbing this input. I also
installed uControl, to see if this program would work, but it didn't have
any mouse mapping options (except some basic things like flipping right to
left). USB Overdrive doesn't detect the bluetooth mouse at all.
If X11 can detect the input, doesn't that mean that on some level, the
native OS can see it too? How can I capture this input and remap it to a
keyboard press (or something else, like a regular right click)?
Thanks in advance for your help,
Dave Margolis
_______________________________________________
bluetooth-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/bluetooth-dev
Do not post admin requests to the list. They will be ignored.