Wayland Protocol for Seat Management

[any1]

Create a new protocol for managing input device seats from wayland clients. This allows us to create a new seat from wayvnc for it to use with virtual input devices.

There are some benefits to using separate seats:

• Using seat0 can mess with the user's selected keyboard layout.
• If multiple users are using the system, they don't have to compete for the pointer. This can be useful when receiving remote tech support via VNC.
• Users have their own sets of active keyboard modifiers (caps lock, shift, ctrl, etc.).

[ammen99]

Is this going to be optional? I.e will wayvnc work also for compositors which do not support this protocol?

[any1]

Is this going to be optional? I.e will wayvnc work also for compositors which do not support this protocol?

This should be optional to begin with because many clients are either not multi-seat capable or buggy in that regard due to little testing having been made with multiple seats.

[bqv]

Does this need to be implemented before https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/61 can be merged?

[any1]

It is implemented already: https://github.com/any1/wayvnc/tree/transient-seats

[any1]

In fact, everything is implemented; just waiting for reviews and acks.