Hi Karl,
On 5/11/22 08:23, k...@aspodata.se wrote:
Fred:
On 5/11/22 05:02, k...@aspodata.se wrote:
You should be able to do lsinput from input-utils package to see which
/dev/input/inputX file your mouse's byte stream transformed as events
would appear. And then run input-events X to see
Fred:
> On 5/11/22 05:02, k...@aspodata.se wrote:
> > You should be able to do lsinput from input-utils package to see which
> > /dev/input/inputX file your mouse's byte stream transformed as events
> > would appear. And then run input-events X to see the events. E.g.:
> >
> > # lsinput | tail
>
Hi Karl,
On 5/11/22 05:02, k...@aspodata.se wrote:
Fred:
...
The Sun Compact 1 three button mouse is 1200 baud, 8 data bits, no
parity and sends 5 bytes in Mouse Systems protocol. Byte 0 is button
info. exactly the same as msc. Byte 1 is 8 bit signed X movement. Byte
2 is 8 bit signed Y
Fred:
...
> The Sun Compact 1 three button mouse is 1200 baud, 8 data bits, no
> parity and sends 5 bytes in Mouse Systems protocol. Byte 0 is button
> info. exactly the same as msc. Byte 1 is 8 bit signed X movement. Byte
> 2 is 8 bit signed Y movement. Bytes 3, 4 are zero.
That fits the
