mirror of
https://gitlab.freedesktop.org/wayland/wayland.git
synced 2025-10-29 05:40:16 -04:00
fix typo
This commit is contained in:
parent
5030af7635
commit
00de1e6cce
2 changed files with 3 additions and 3 deletions
2
README
2
README
|
|
@ -12,7 +12,7 @@ buffer management. The compositor receives input events and forwards
|
|||
them to the relevant client. The clients creates buffers and renders
|
||||
into them and notifies the compositor when it needs to redraw. The
|
||||
protocol also handles drag and drop, selections, window management and
|
||||
other interactions that must go throught the compositor. However, the
|
||||
other interactions that must go through the compositor. However, the
|
||||
protocol does not handle rendering, which is one of the features that
|
||||
makes wayland so simple. All clients are expected to handle rendering
|
||||
themselves, typically through cairo or OpenGL.
|
||||
|
|
|
|||
4
TODO
4
TODO
|
|
@ -1,8 +1,8 @@
|
|||
Core wayland protocol
|
||||
|
||||
- We need rotation information in the output (multiples of 90
|
||||
degress) and we'll need a way for a client to communicate that it
|
||||
has rendered it's buffer according to the output rotation. The
|
||||
degrees) and we'll need a way for a client to communicate that it
|
||||
has rendered its buffer according to the output rotation. The
|
||||
goal is to be able to pageflip directly to the client buffer, and
|
||||
for that we need the client to render accordingly and the
|
||||
compositor needs to know that it did.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue