mirrors/wayland
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/wayland/wayland.git synced 2025-10-29 05:40:16 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

doc: fix and clarify pointer image behaviour

Browse source 
Signed-off-by: Yann Dirson <ydirson@free.fr>
This commit is contained in:
Yann Dirson 2020-03-30 18:29:08 +02:00 • committed by Daniel Stone
parent df969706f4
commit ef611a803e
1 changed files with 8 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

12
doc/publican/sources/Protocol.xml
View file

@ -400,11 +400,12 @@
request is ignored. To the client this will look like it successfully request is ignored. To the client this will look like it successfully
set the pointer image. set the pointer image.
</para> </para>
<para>
Setting the pointer image to NULL causes the cursor to be hidden.
</para>
<para> <para>
The compositor will revert the pointer image back to a default 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 when no surface has the pointer focus for that device.
revert the pointer image back to the default image by setting a NULL
image.
</para> </para>
<para> <para>
What if the pointer moves from one window which has set a special What if the pointer moves from one window which has set a special
@ -412,7 +413,10 @@
the motion event? The new surface will be stuck with the special the motion event? The new surface will be stuck with the special
pointer image. We can't just revert the pointer image on leaving a pointer image. We can't just revert the pointer image on leaving a
surface, since if we immediately enter a surface that sets a different surface, since if we immediately enter a surface that sets a different
image, the image will flicker. Broken app, I suppose. image, the image will flicker. If a client does not set a pointer image
when the pointer enters a surface, the pointer stays with the image set
by the last surface that changed it, possibly even hidden. Such a client
is likely just broken.
</para> </para>
</section> </section>
<section id="sect-Protocol-Output"> <section id="sect-Protocol-Output">