On Thu, 14 Sep 2023 15:10:48 -0400
jleivent wrote:
> On Thu, 14 Sep 2023 16:32:06 +0300
> Pekka Paalanen wrote:
>
> >
> > As an aside, we collect unfixable issues under
> > https://gitlab.freedesktop.org/wayland/wayland/-/issues/?label_name%5B%5D=Protocol-next
> > These are issues that are eit
On Thu, 14 Sep 2023 12:24:42 +0100
John Cox wrote:
> Hi
>
> A, hopefully, simple question - should I expect a wl_buffer::release
> event from the buffer previously committed to a surface after I've
> attached (and invalidated & committed) a NULL buffer to the surface? it
> doesn't seem to happen
Hi
>On Thu, 14 Sep 2023 12:24:42 +0100
>John Cox wrote:
>
>> Hi
>>
>> A, hopefully, simple question - should I expect a wl_buffer::release
>> event from the buffer previously committed to a surface after I've
>> attached (and invalidated & committed) a NULL buffer to the surface? it
>> doesn't s
On Fri, 15 Sep 2023 14:12:25 +0100
John Cox wrote:
> Hi
>
> >On Thu, 14 Sep 2023 12:24:42 +0100
> >John Cox wrote:
> >
> >> Hi
> >>
> >> A, hopefully, simple question - should I expect a wl_buffer::release
> >> event from the buffer previously committed to a surface after I've
> >> attached
> Ideally the release event would have been a wl_callback just like
> wl_surface.frame is.
I sent [1] to fix this.
[1]: https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/137
