On Sun, 22 Jan 2006 14:34:54 +0100 (CET) Michael Schmitz <[EMAIL PROTECTED]> wrote:
> > Well, no luck, it's not that easy. Neither the fact that mouseemu is > > running in parallel, nor the order in which thez are started seems to > > matter. There are a couple of applications fiddle around with /dev/input/event so I try to bring some light into it. Udev is responsible for creating an /dev/input/event% device for each HID. Udev is the most comfortable way to have up-to-date devices in /dev. If you don't have udev running, be sure that each HID is represented by an event devive in /dev/input/. Pbbuttonsd opens all /dev/input/event% devices and uses them for input (at least to reset the user idle timer). If autorescan = yes (which should be set by default now), devices will be automatically added or removed as soon as they appear or vanish. So called 'fake' devices, created for example by the uinput kernel driver, will be used as usual. Pbbuttonsd makes no difference between a real event device or one from uinput. With the new beta version there is no limit anymore for used event devices. In worst case all 32 devices will be read. Mouseemu exclusively locks all input devices related to mice for full control. After that it routes the mouse events through a newly created input device (or two of them). This way it can filter out unwanted mouse events or create new ones. Pbbuttonsd can't access the locked event devices anymore but it uses the newly created uinput devices instead. You won't see any difference in behaviour. Synaptics Trackpad driver, often used on recent PowerBooks, also locks all mouse input events for exclusive use but in contrast to mouseemu it doesn't create an uinput device to let other applications receive mouse events. This problem is well known and Luca Bigliardi prepared a patch to work around this problem. Furthermore some people including Luca are working on a final solution of this problem. If you used the unmodified synaptics driver you would deprive pbbuttonsd and mouseemu of mouse events. I hope this will help to identify where the problems come from or at least give some hinte where to look at next. Best Regards Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
