[PATCH wayland] protocol: when buffer transform and scale change

[ppaalanen at gmail.com]

From: Pekka Paalanen <pekka.paalanen at collabora.co.uk>

Clarify when the pending and current buffer transform and scale values
change, and what exactly happens on commit.

This matches what Weston currently does.

Signed-off-by: Pekka Paalanen <pekka.paalanen at collabora.co.uk>
---
 protocol/wayland.xml | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/protocol/wayland.xml b/protocol/wayland.xml
index bf6acd1..e1edbe5 100644
--- a/protocol/wayland.xml
+++ b/protocol/wayland.xml
@@ -1201,6 +1201,11 @@
 
 	A newly created surface has its buffer transformation set to normal.
 
+	wl_surface.set_buffer_transform changes the pending buffer
+	transformation. wl_surface.commit copies the pending buffer
+	transformation to the current one. Otherwise, the pending and current
+	values are never changed.
+
 	The purpose of this request is to allow clients to render content
 	according to the output transform, thus permiting the compositor to
 	use certain optimizations even if the display is rotated. Using
@@ -1227,6 +1232,10 @@
 
 	A newly created surface has its buffer scale set to 1.
 
+	wl_surface.set_buffer_scale changes the pending buffer scale.
+	wl_surface.commit copies the pending buffer scale to the current one.
+	Otherwise, the pending and current values are never changed.
+
 	The purpose of this request is to allow clients to supply higher
 	resolution buffer data for use on high resolution outputs. Its
 	intended that you pick the same	buffer scale as the scale of the
-- 
1.8.3.2