protocol: prefer wl_surface.damage_buffer
This commit makes wl_surface.damage_buffer preferred over wl_surface.damage.
wl_surface.damage can be implemented in a non-optimal way by the compositor
(e.g. by always damaging the whole buffer).
Having two requests makes it complicated for the compositor to handle damage,
making it necessary to transform one into the other's coordinates.
Moreover, integration with wp_viewporter is tricky.
Signed-off-by: Simon Ser <contact@emersion.fr>
Acked-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
Reviewed-by: Derek Foreman <derek.foreman.samsung@gmail.com>
Simon Ser authored 5 years ago
Derek Foreman committed 5 years ago
| 1396 | 1396 | and clears pending damage. The server will clear the current |
| 1397 | 1397 | damage as it repaints the surface. |
| 1398 | 1398 | |
| 1399 | Alternatively, damage can be posted with wl_surface.damage_buffer | |
| 1400 | which uses buffer coordinates instead of surface coordinates, | |
| 1401 | and is probably the preferred and intuitive way of doing this. | |
| 1399 | Note! New clients should not use this request. Instead damage can be | |
| 1400 | posted with wl_surface.damage_buffer which uses buffer coordinates | |
| 1401 | instead of surface coordinates. | |
| 1402 | 1402 | </description> |
| 1403 | 1403 | <arg name="x" type="int" summary="surface-local x coordinate"/> |
| 1404 | 1404 | <arg name="y" type="int" summary="surface-local y coordinate"/> |