Quote:
Originally Posted by lucida
I do this in every one minute because I wasn't sure about the load of the command at that time(seems minimal though). Should have no problem to run it on every touch.
and mouseturn is different from evdev as it relies on /dev/input/mice so it's plug&play, sth. like this.
And if you have multiple devices you can run multiple instances of kindle-evdev or try this updated version. it goes like
kindle-evdev2 -f /dev/input/eventX /dev/input/eventY ... -c key1:x,y key2:x,y..... |
Thanks, although no source - but it's not a problem because:
I am in the process of changing kindle-evdev to make it check all /dev/input/eventX devices for the keys specified in a config file.
Do you think it is 'bad' for the battery to be constantly checking /dev/input/event0 /dev/input/event1 /dev/input/event2 etc?
Plus I want the user to be able to remove the usb device and insert without problems, so the list of input event devices will be checked and repopulated every 10 seconds/30 seconds/1 minute.
I am happy to code this myself, but do you see any problems?
I'm just worried that this constant checking will impact the device somehow, I wouldn't want that.
Thanks for your work!