mirror of
https://gitlab.freedesktop.org/libinput/libei.git
synced 2026-01-07 08:50:14 +01:00
proto: Small grammar changes to stylus protocol
This commit is contained in:
parent
b95174849e
commit
499633efd2
1 changed files with 4 additions and 4 deletions
|
|
@ -1604,12 +1604,12 @@
|
|||
required to negotiate tool capabilities. Negotiation is performed by the
|
||||
server first sending ei_stylus.tool_capabilities prior to ei_device.done
|
||||
and then the client responding with ei_stylus.bind_tool_capabilities
|
||||
prior to starting emulation for the first time.
|
||||
prior to ei_device.ready.
|
||||
|
||||
This interface may be used on both ei_device.device_type.virtual and
|
||||
ei_device.device_type.physical devices. As an interface with absolute
|
||||
motion, virtual devices must declare an arbitrary set of regions that
|
||||
are be valid for motion events. For physical devices, the server must
|
||||
are valid for motion events. For physical devices, the server must
|
||||
send an ei_device.dimensions that reflects the size of the active area
|
||||
of the stylus' digitizer. This size **must not** include any
|
||||
"[out-of-bounds][OOB]" margin that may exist (e.g. a digitizer with a
|
||||
|
|
@ -1872,7 +1872,7 @@
|
|||
location that exists outside of these locations. The EIS implementation
|
||||
may clamp out-of-range values and/or disconnect the client.
|
||||
|
||||
This request is required to be in the same frame as
|
||||
This request must be in the same frame as
|
||||
ei_stylus.proximity_in. It may also be sent while the stylus is in or
|
||||
leaving proximity. It is a protocol violation to send this request at
|
||||
any other time.
|
||||
|
|
@ -2022,7 +2022,7 @@
|
|||
<description summary="stylus tool capabilities event">
|
||||
See the ei_stylus.bind_tool_capabilities request for more details.
|
||||
|
||||
The server sends this event after attaching the ei_stylus interface
|
||||
The server sends this event after announcing the ei_stylus interface
|
||||
to an ei_device. This event describes the set of capabilities that
|
||||
the tool supports. For sender contexts, the client must confirm
|
||||
(and optionally narrow down) the capabilities with the
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue