On 11/5/18 1:44 PM, Derek Foreman wrote:
> On 11/5/18 7:57 AM, Simon Ser wrote:
>> 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
On 11/5/18 7:57 AM, Simon Ser wrote:
> 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 compo
On Mon, 05 Nov 2018 13:57:00 +
Simon Ser wrote:
> 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 complica
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
