mirrors/wayland
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/wayland/wayland.git synced 2026-02-26 01:40:41 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fixes after @mahkoh review

Browse source 
Signed-off-by: Pierre Le Marre <dev@wismill.eu>
This commit is contained in:
Pierre Le Marre 2025-11-28 12:13:15 +01:00
parent 4380e5ddb9
commit 715d52d40f
No known key found for this signature in database
GPG key ID: 3BFB00E5C59E818E
1 changed files with 26 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

42
protocol/wayland.xml
View file

@ -2038,6 +2038,32 @@
</description>
</request>
<!-- Version 11 additions -->
<request name="get_keyboard_with_formats">
<description summary="return keyboard object">
The ID provided will be initialized to the wl_keyboard interface
for this seat.
This is an alternative to get_keyboard that informs the server of the
keymap formats supported by the client. The server selects one of the
provided format that it supports itself and may start to send keyboard
events. It is advised, but not mandatory, to respect the client’s order
of preference of the formats.
TODO: what if none of the format is supported?
This request only takes effect if the seat has the keyboard
capability, or has had the keyboard capability in the past.
It is a protocol violation to issue this request on a seat that has
never had the keyboard capability. The missing_capability error will
be sent in this case.
</description>
<arg name="id" type="new_id" interface="wl_keyboard" summary="seat keyboard"/>
<arg name="formats" type="array"
summary="A list of keymap_format values, ordered by preference"/>
</request>
</interface>
<interface name="wl_pointer" version="11">
@ -2649,22 +2675,6 @@
<!-- Version 11 additions -->
<request name="set_supported_keymap_formats" since="11">
<description summary="set the keymap formats supported by the client">
Inform the server of the keymap formats supported by the client, in
ascending order.
If none of the formats is supported by the server, then a
no_supported_keymap_format error is triggered.
Otherwise the server selects one of the provided format that it supports
itself and may start to send keyboard events. It is advised, but not
mandatory, to select the format with most features.
</description>
<arg name="formats" type="array"
summary="A list of keymap_format values, in ascending order"/>
</request>
<enum name="error" since="11">
<entry name="no_supported_keymap_format" value="0" since="11"
summary="none of the keymap formats provided by the client is supported"/>