On Fri, 22 Sep 2023 15:47:13 +0100
John Cox wrote:
> Hi
>
> >On 9/14/23 14:24, 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 &
Hi
>On 9/14/23 14:24, 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 for
On 9/14/23 14:24, 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 for me (I have
On Fri, 15 Sep 2023 21:53:34 +, you wrote:
>> 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
That would have been nice but it doesn't look like
> 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
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
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
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
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 for me (I have WAYLAND_DEBUG=1 logs showing it
not happening).