[PATCH weston] input: don't send to clients key events eaten by bindings

Pekka Paalanen ppaalanen at gmail.com
Wed Nov 19 03:40:28 PST 2014


On Thu, 13 Nov 2014 09:53:56 +0000
Daniel Stone <daniel at fooishbar.org> wrote:

> Hi,
> 
> On Thursday, November 13, 2014, Daniel Stone <daniel at fooishbar.org> wrote:
> >
> > On 13 November 2014 07:35, Pekka Paalanen <ppaalanen at gmail.com
> > <javascript:_e(%7B%7D,'cvml','ppaalanen at gmail.com');>> wrote:
> >
> >> On Wed, 12 Nov 2014 12:06:16 -0800
> >> Bill Spitzak <spitzak at gmail.com
> >> <javascript:_e(%7B%7D,'cvml','spitzak at gmail.com');>> wrote:
> >> > The important point is that in both your and my case the client that has
> >> > just received focus sees the 'd' as being held down. The 'd' is on in
> >> > the key-down array attached to the focus-in event!!!!
> >>
> >> Correct. Apparently X apps interpret a "key already down" the same way
> >> as a "key goes down" event. That is not a Wayland issue at all.
> >
> >
> > No, X _apps_ don't - XWayland does.
> >
> 
> To be clear: X11 has this as well. FocusIn + KeymapNotify events are
> equivalent to wl_keyboard::enter with a fully-populated key list.

Ah, I didn't know that. Since there was a problem here, I assumed
X11 as a protocol has no way to differentiate between that and key.

It's all starting to make sense now. I think.


Thanks,
pq


More information about the wayland-devel mailing list