00:00 RAOF: Why would you want the mask to be a wl_surface?
00:01 RAOF: nullpointer128: If you wanted to use a 1-channel `wl_buffer` as a mask (like you're doing fancy input shaping or something) you could just... add a request associating a 1-channel `wl_buffer` to a `wl_surface`.
00:03 RAOF: That way you'd get integration with all the double-buffered wl_surface state.
00:04 nullpointer128: Which object should I add the request to, or should I have my own object that has that request?
00:05 nullpointer128: I'm hoping to draft a background blur protocol where clients can set a blur mask for the contents behind the mask to be blurred
00:06 nullpointer128: The hope is to support exotic window shapes which aren't just rectangles
00:25 RAOF: Ok. So, you'd want a factory object that takes a wl_surface and gives you a ext_blur_mask or something; then you'd have ext_blur_mask have a set_mask request taking a wl_buffer.
00:25 RAOF: https://wayland.app/protocols/kde-blur is a little similar.
00:29 RAOF: You'd likely want to specify that the set_mask is double-buffered state, gated on wl_surface.commit() as normal.
00:38 nullpointer128: Forgot to reply, thanks RAOF
05:08 wlb: wayland Issue #355 closed \o/ (Simulate/automate mouse and keyboard events https://gitlab.freedesktop.org/wayland/wayland/-/issues/355)
10:07 pq: emersion, thanks for the release! Did you forget to cc linux-media or intentionally?
10:10 emersion: pq: ah, no, i didn't think about that, goods point
10:10 emersion: good*
10:14 pq: emersion, I have nothing planned for Wayland, so any schedule is fine by me.
10:29 wlb: wayland Issue #356 opened by Alexandros Frantzis (afrantzis) RFC: Provide a mechanism for notifying when a wl_event_queue has events to dispatch https://gitlab.freedesktop.org/wayland/wayland/-/issues/356
11:58 wlb: wayland/main: Simon Ser * readme: drop paragraph about Weston https://gitlab.freedesktop.org/wayland/wayland/commit/8ffd7db24f90 README
11:58 wlb: wayland/main: Simon Ser * readme: reword website description https://gitlab.freedesktop.org/wayland/wayland/commit/20498d9ea189 README
11:58 wlb: wayland/main: Simon Ser * readme: convert to Markdown https://gitlab.freedesktop.org/wayland/wayland/commit/a782152de0f0 README.md
11:58 wlb: wayland Merge request !294 merged \o/ (readme: update and convert to Markdown https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/294)
12:27 wlb: wayland Issue #357 opened by Matthias Clasen (matthiasc) Clarify the intended semantics of attach vs offset in version >= 5 https://gitlab.freedesktop.org/wayland/wayland/-/issues/357
12:44 wlb: wayland Merge request !295 opened by Sebastian Wick (swick) protocol: do not change pending x and y when attaching a buffer https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/295
13:17 pq: merged...
13:18 pq: is wlb intentionally not reporting Weston stuff?
13:27 daniels: I have no idea; I gave up re-enabling it weeks ago
13:44 pq: but wayland stuff comes through fine?
16:12 emersion: pq, so should it do libdisplay-info 0.1.1 or 0.2.0 ?