-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 1 Dec 2002 10:14, [EMAIL PROTECTED] wrote:
> Firstly, the Z-axis relates to a little blue button on the top of the
> mouse that is very much like the cursor in the center of a thinkpad laptop
> (i.e. IBM producing a microsoft intellimouse type device with their own
> patents). I think the output suggests that it actually records movement in
> two axis which suggests that it ought to be used for controlling screen
> scroll-bars?!?
OK, so it effectively a horizontal and vertical wheel.
> (Moving little blue button up...)
>
> Event: time 1038686594.818629, type 2 (Relative), code 0 (X), value -1
> Event: time 1038686594.858633, type 2 (Relative), code 8 (Wheel), value 63
> Event: time 1038686594.858638, type 2 (Relative), code 2 (Z), value 19
> Event: time 1038686594.882616, type 2 (Relative), code 0 (X), value 1
Your accuracy isn't too good:-) You are getting a lot of left-right when using
the button in an up-down direction. You are moving the mouse too (that the X
part).
Can you try to get results that _only_ have Wheel or Z results? Is it
physically possible?
Also, looks like IBM didn't understand what the HID usage tables were telling
them. The button should probably have been implemented to return information
corresponding to horizontal and vertical wheels. Z has completely different
meaning.
> Using the read-event.c file you kindly sent me I get nothing for mouse
> movements, only for button clicks :
I screwed up and sent you a version that filters for only buttons. You can fix
this by taking out the test for type==EV_KEY. However it is better to use
evtest, which does the same thing, only better.
Generally, the mouse is HID compliant, and is working perfectly from a USB
point of view. The input layer also seems to be reporting the information
correctly. If you want to use the vertical direction on your mouse as a
wheel, then you just need to do the normal X magic, which basically means
adding something like the following to your XF86Config-4:
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
EndSection
If that isn't clear, look at the X docs (or Google, this has been asked and
documented a lot of times before). This is NOT a USB problem, so you'd be
better off asking for help on an X list, if required.
I'll answer the superpen stuff in a second email. It is going to take me a
while though.
Brad
- --
http://linux.conf.au. 22-25Jan2003. Perth, Aust. I'm registered. Are you?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE96e5HW6pHgIdAuOMRAgDTAKCyBTQSUJI2QHGGBHNVeMFfdJxodwCeNk4X
jL5EJj8zE6dzh9paWeM7+fE=
=S3fC
-----END PGP SIGNATURE-----
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
