mirror of
https://gitlab.freedesktop.org/libinput/libei.git
synced 2026-02-04 14:10:27 +01:00
README: Xwayland is a Wayland client
Xwayland is not a compositor, it's a Wayland client. Also fix a few typos while at it (XWayland -> Xwayland). Signed-off-by: Olivier Fourdan <ofourdan@redhat.com>
This commit is contained in:
parent
a6ea982bca
commit
1ef00d449c
1 changed files with 3 additions and 3 deletions
|
|
@ -310,7 +310,7 @@ the compositor instead.
|
|||
| libinput | libeis | \_wayland______
|
||||
+----------+---------+ \
|
||||
| | +-------+------------------+
|
||||
/dev/input/ +---brei----| libei | XWayland |
|
||||
/dev/input/ +---brei----| libei | Xwayland |
|
||||
+-------+------------------+
|
||||
|
|
||||
| XTEST
|
||||
|
|
@ -319,7 +319,7 @@ the compositor instead.
|
|||
| X client |
|
||||
+-----------+
|
||||
```
|
||||
Of course, XWayland is just another Wayland compositor, so the connection
|
||||
Of course, Xwayland is just another Wayland client, so the connection
|
||||
between libei and libeis could be handled through a portal.
|
||||
|
||||
### Short-lived applications
|
||||
|
|
@ -340,7 +340,7 @@ re-ordering input events and cause havoc.
|
|||
|
||||
It could be `libei` itself to implement these event queues but this too can
|
||||
mess with the input order. And implementing an event queue is not hard, so
|
||||
this issue is punted to the caller instead. XWayland in its current
|
||||
this issue is punted to the caller instead. Xwayland in its current
|
||||
implementation already does this.
|
||||
|
||||
### uinput vs libei
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue