[PATCH] Extending wayland protocol for helping a wayland client to identify the event source of device (pointer/keyboard)

Bill Spitzak spitzak at gmail.com
Fri Sep 25 10:06:20 PDT 2015

On Fri, Sep 25, 2015 at 2:14 AM, Pekka Paalanen <ppaalanen at gmail.com> wrote:

You don't need multiple seats.

The remote control would simply not be a "keyboard". It can send
wl_pointer::button events for the buttons. Note that they have exactly the
same format as wl_keyboard::key. There is a reason for this. The clients
can distinguish between wl_pointer::button and wl_keyboard::key events, and
the compositor is already set up to deliver these to different clients. So
it satisfies the stated need.

If your api requires more than these 2 foci then either you add extensions
to the compositor to support more foci or you use multiple seats. But the
stated problem needs no more than 2 seats, since you only listed two
destinations for the events.

I am not clear on how the client with the pointer focus can figure out what
modifiers are down however. But if the remote has modifiers I think users
expect them to act global, ie holding the Shift on the remote is the same
as holding Shift on the keyboard.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20150925/df7e2276/attachment.html>

More information about the wayland-devel mailing list