Originally Posted by jolouis

Hi Larry,

I'm going to play around with the scratchbox Live CD this weekend to try and recompile X/Kdrive myself also, but I'm curious about your experience. Once you had it compiled did you make sure you added the second mouse driver to the KDrive startup command? According to everything I've read you should have been able to have both a regular mouse and tslib active using something along these lines:

ARGS="-mouse tslib -mouse mouse -nozap -dpi $DISPLAY_DPI -wr -nolisten tcp"

Originally Posted by jolouis

The reason that it doesn't work/crashes KDrive on the tablets right now is that the "mouse" driver isn't compiled in; I don't know if you looked through the source code before you compiled, but there's definitely something that has this driver disabled from compiling in the default setup (I'd imagine there's an option in the Makefile that's flagged out, but I haven;t looked at it yet); the source for the mouse driver is there, it's just not compiled in.

Thanks,
-Rob

Originally Posted by Benson

Allright, here's the new version. You no longer need a .evrouterrc; it makes that on-the-fly (under a different name). If you do have one, it will be included in the created file, so if you use evrouter to rebind keys or touchscreen events, that'll still work.

This probably won't work with two mice hooked up. If it does, only one will work. If someone wants to post patches for multiple mice, that's great, but it's too much hassle for me, and I couldn't test it anyway...

Code:

#!/bin/sh
killall evrouter mouse_poll
rm /tmp/.evrouter\:0.0

for devfile in /dev/input/event*; do
  sudo /bin/chmod a+r $devfile
done 

device="/dev/input/`awk '/^H.*mouse/ {print $NF}' </proc/bus/input/devices`"
if [ "$device" != /dev/input/ ] ; then 
  echo "Device found: $device"
else
  echo "No device found! Aborting."
  exit 1
fi

cat >~/.evrouterrc_auto < ~/.evrouterrc
sed "s/dev/$device/" >~/.evrouterrc_auto << E_O_F
Window ""
"" "dev" any key/272 "XButton/1"
"" "dev" any key/273 "XButton/3"
"" "dev" any key/274 "XButton/2"
"" "dev" any rel/8/1 "XKey/Up"
"" "dev" any rel/8/-1 "XKey/Down"
E_O_F

mouse_poll $device&
evrouter -c ~/.evrouterrc_auto /dev/input/event*&

while [ "x`grep '^H.*mouse' /proc/bus/input/devices`" != x ]; do
  sleep 5
done

killall evrouter mouse_poll

By the way, reason I didn't warn anyone about the unplugging issue: I'm hardly aware of it, because everytime I unplug the mouse, it's to plug it back into my desktop. So I'm leaving the adapter in the N800, and going back and forth. I'll be even more grateful for your (presumed) fix when I get around to buying a little mouse for the N800.

Originally Posted by Benson

Don't know; dragging works fine for me, but I don't use any chording shortcuts...

One issue I have sometimes, that I've not been able to diagnose, is that sometimes the primary button works by itself, in which case evrouter dumps a second click, and left-click becomes left-double-click. Intermittent, and not enough hassle to figure out what circumstances trigger it.

Since yours seems to be sending different key codes (110-1, instead of 272-4), I don't think evrouter is doing anything helpful. You're just getting the (intermittent) automatic click support.

Also, the currently "supported" way to get mouse support is with jolouis's package. But the script is pretty much the same...

Originally Posted by Benson

I'm fixing to install Diablo (the real thing, not the hacked-up version we were using before release) today; once I get that, I'm planning to do some testing on this...