On Mon, 27 Mar 2006 14:23:11 +0200 (CEST), "Michael Schmitz" <email@example.com> said:
> The state of the modifier key is kept by the X server, so you need
> to send the modifier before you send a regular key event
> (disregarding mouse events for a moment here). We could postpone the
> modifier event until we know what other event follows, but that's
> equally messy.
I kind-of worked out a state machine to do this sort of thing; the
result was horrible.
> > Later on today I will have at look at the behaviour of Apple X11, and
> > check out what events it is generating.
> Right, they must have solved this some way already.
Yep, it just seems to send a modifier-up, button-click, modifier-down
when the mouse is clicked.
> Should not really happen, because mouseemu intercepts all input events
> hopefully, and hence can ensure they get sent in the correct order.
> Meaning you cannot sneak a key event in between the mod up, mouse down,
> mod down sequence. IIRC X doesn't mind if the modifier state changes
> a button is kept down. Either way, there's limits to what extent you can
> emulate mouse buttons using modifier keys.
> I'll cook up some experimental hack for you to test.
That would be really cool!
http://www.fastmail.fm - Does exactly what it says on the tin
- Re: mouseemu
- From: Michael Schmitz <firstname.lastname@example.org>