> > Line 232 of mouseemu.c:
> >
> > register_inputhandler(fd, keyboard_handler, 1);
> >
> > Change that 1 to 0 and key events are passed on to pbbuttonsd (I imagine
> > the mouse register device call needs the same change to let pbbuttonsd
> > react to mouse moves).
>
> I have tested this and after restarting both mouseemu and pbbuttonsd, i
> got the pbbuttonsd keys back. This seems to fix #307068 as well.
I had to comment out the passthrough() call in the keyboard event handler
as well BTW. Otherwise keypresses would show up twice (on key release) in
the shell. Didn't happen every time though.
> > Side effect: the 3~ crap on pasting with the mouse is back.
> >
> > I've played a bit with the event passthrough mechanism (sending sync
> > events after passed key events) to no avail.
>
> I don't know what sort of crap that could be. Copy paste seems to work
> just fine from both the mouse and the keyboard here.
That's the ordinary F11 keysym being received by the terminal app. I
could solve that by hacking the X keymap. I'd rather have the option to
_not_ send a button and a key event on F11 (that's what happens with
mouseemu grabbing the events: the key event is translated into a button
event, and only that one is sent). So we'd explicitly need to delete the
key event from the event queue here. No idea how to do that. No idea why
passing the brightness button events through to pbbuttonsd doesn't work,
either (are there raw as opposed to cooked events?).
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
