summaryrefslogtreecommitdiff
path: root/spec
diff options
context:
space:
mode:
authorKristian Høgsberg <krh@bitplanet.net>2010-08-16 10:38:29 -0400
committerKristian Høgsberg <krh@bitplanet.net>2010-08-16 10:38:29 -0400
commit77fb1679566566d881f16d2547d8b00857dc55bc (patch)
tree92e1dd134b8a930454db706f22053a98b027b211 /spec
parentb036ad4a9ac53def327b80203ab3aaebe709744c (diff)
Add protocol for setting the pointer image
Diffstat (limited to 'spec')
-rw-r--r--spec/main.tex18
1 files changed, 9 insertions, 9 deletions
diff --git a/spec/main.tex b/spec/main.tex
index 330d672..41e0367 100644
--- a/spec/main.tex
+++ b/spec/main.tex
@@ -159,7 +159,7 @@ delivered in both screen coordinates and surface local coordinates.
\hline
Interface \texttt{cache} \\ \hline
Requests \\ \hline
- no requests \\ \hline
+ \texttt{attach(buffer, x, y)} \\
Events \\ \hline
\texttt{motion(x, y, sx, sy)} \\
\texttt{button(button, state, x, y, sx, sy)} \\
@@ -179,14 +179,14 @@ Talk about:
A surface can change the pointer image when the surface is the pointer
focus of the input device. Wayland doesn't automatically change the
pointer image when a pointer enters a surface, but expects the
-application to set the cursor it wants in response the the motion
-event. The rationale is that a client has to manage changing pointer
-images for UI elements within the surface in response to motion events
-anyway, so we'll make that the only mechanism for setting changing the
-pointer image. If the server receives a request to set the pointer
-image after the surface loses pointer focus, the request is ignored.
-To the client this will look like it successfully set the pointer
-image.
+application to set the cursor it wants in response the the pointer
+focus and motion events. The rationale is that a client has to manage
+changing pointer images for UI elements within the surface in response
+to motion events anyway, so we'll make that the only mechanism for
+setting changing the pointer image. If the server receives a request
+to set the pointer image after the surface loses pointer focus, the
+request is ignored. To the client this will look like it successfully
+set the pointer image.
The compositor will revert the pointer image back to a default image
when no surface has the pointer focus for that device. Clients can