On Sun, Sep 09, 2001 at 02:36:27PM -0400, Brian S. Julin wrote:
| On Sun, 9 Sep 2001, dman wrote:
| > Shouldn't that be GII_INPUT? Well, I tried GII_INPUT (and just now
| > noticed it was different in the mail) and it works, but no scroll
| > wheel yet.
|
| Only use GII_INPUT if you are using LibGII without LibGGI. Use
| GGI_INPUT for GGI programs like inputdump. Try that program,
Oh, ok.
| BTW. I just re-verified that when I do
| GGI_INPUT=linux-evdev:/dev/input/event2 inputdump
| I see wheel events from the mouse on the W axis from the evdedv source
| (you may have other sources, such as the xwin, sending duplicate events.)
I found that I had to compile inputdump myself. (The debian package
"libggi-samples" had it as gzipped source only) Not bad -- all I had
to do was add '-lggi' to gcc (and compile the other demo 'giik2str'
that it depended on).
When I run it I get 3 sections on the screen labeled "Linux Keyboard",
"Raw Mouse", and "Logitech USB-PS/2 Mouse M-BA47". The keyboard part
looks ok, as far as I can tell (but I'm not looking up the ASCII codes
because the keyboard seems to work fine in quake).
The Raw Mouse part has very erratic data for mx, my, and 3 buttons.
Scrolling the wheel has an effect, but not what is intended. Is this
trying to use "linux-mouse"?
The "Logitech" mouse quadrant displays the correct data for mx, my,
mw, and button 01, 02, 03, and 04. It displays (in white, not green)
? 0
? 1
? 2
? 3
? 4
? 5
? 6
? 7
? 8
? 9
? 10
? 11
abouve the 'mx', 'my', etc. I don't know what that means.
However, in quake and XGGI the linux-evdev stuff isn't working right.
The keyboard works fine though. I think that I had the correct
settings in /etc/ggi/input/linux-mouse and gii used that when I tried
to test it before. Does the app have to do anything to use the event
stuff correclty? I would think not, but inputdump works while quake
and XGGI don't.
-D
