fdo-mirrors/libei
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/libinput/libei.git synced 2025-12-30 15:20:09 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

proto: clarify that the ei_seat capabilities depend on ei_device

Browse source 
Regardless of the ei_seat version, ei_seat.bind will support all
capablities of the negotiated ei_device interface. This means we don't need
to bump ei_seat just to add a new capability to ei_device.
This commit is contained in:
Peter Hutterer 2023-03-06 10:30:32 +10:00
parent 717900f6fe
commit ebd7d102cd
1 changed files with 11 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
proto/protocol.xml
View file

@ -571,7 +571,12 @@
capabilities provided in the ei_seat.capabilities event. That event's capabilities
are used as a mask of capabilities that can be bound.
Binding capabilities that are not supported in the ei_seat's interface version
Note that available seat capabilities are defined in the ei_device
interface and not dependent on the seat interface version. In other
words, ei_seat.bind supports any capability available in the
client-announced ei_device interface version.
Binding capabilities that are not supported in the ei_device's interface version
is a client bug and may result in disconnection.
A client may send this request multiple times to adjust the capabilities it
@ -611,6 +616,11 @@
capabilies and an EIS implementation may then create device based on the bound
capabilities.
Note that available seat capabilities are defined in the ei_device
interface and not dependent on the seat interface version. In other
words, ei_seat.bind supports any capability available in the
client-announced ei_device interface version.
Note that seat capabilities only represent a mask of possible capabilities on
devices in this seat. A capability that is not available on the seat cannot
ever be available on any device in this seat. For example, a seat that only has the