Further mouse tests

well - an update to my mouse/FB-con probs:
with SDL debug info I’m getting:

Using HID mouse
Read 3 bytes from mouse, start = 0
Read 6 bytes from mouse, start = 3
Read 5 bytes from mouse, start = 2
Read 4 bytes from mouse, start = 1
Read 3 bytes from mouse, start = 0
Read 6 bytes from mouse, start = 3
Read 5 bytes from mouse, start = 2
Read 4 bytes from mouse, start = 1
Read 3 bytes from mouse, start = 0

Now the only thing I’ve spotted so far in SDL that makes me go hmm is
that the event handler for IMPS2 seems to expect a 4-byte packet and this
is going from 3 to 6 bytes… am I missing something?

PS: I’ll fix it myself if someone would be so kind as to point me to, say,
specs for IMPS2 mouse g. gpm is -too- convoluted and besides SDL asks
some data that gpm doesn’t (such as wheel data). And the actual
event-decode in SDL looks fine anyways - I suspect the problem is
elsewhere.

Could even be a linux-2.4.5 artifact but I doubt it as all other mouse
apps that I have operate properly.

TIA and G’day, eh? :slight_smile:
- Teunis

well - an update to my mouse/FB-con probs:
with SDL debug info I’m getting:
[…]

If it makes you feel any better, I just tried it here, and I get the same
results; mouse all over the place. I’ll look into it, unless someone else
pipes up with a patch first.

–ryan.