08:48wlb: weston/main: Arnaud Vrac * desktop-shell: clamp view alpha correctly https://gitlab.freedesktop.org/wayland/weston/commit/14e0fff19afe desktop-shell/shell.c
08:48wlb: weston/main: Arnaud Vrac * desktop-shell: set proper curtain size when no output is created yet https://gitlab.freedesktop.org/wayland/weston/commit/03fa71f15350 desktop-shell/shell.c
08:48wlb: weston/main: Arnaud Vrac * clients/desktop-shell: fix crash on init when panel is disabled https://gitlab.freedesktop.org/wayland/weston/commit/59207a7c7ce9 clients/desktop-shell.c
08:48wlb: weston Merge request !1398 merged \o/ (Desktop shell fixes https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1398)
09:42wlb: weston Merge request !1391 merged \o/ (replace weston_signal_emit_mutable with wl_signal_emit_mutable https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1391)
09:42wlb: weston/main: He Yong * replace weston_signal_emit_mutable with wl_signal_emit_mutable https://gitlab.freedesktop.org/wayland/weston/commit/98606d6a0394 ivi-shell/ivi-layout.c libweston/compositor.c libweston/pixman-renderer.c tests/safe-signal-output-removal-test.c tests/safe-signal-test.c
09:42wlb: weston/main: He Yong * libweston: remove wlr_signal_emit_safe https://gitlab.freedesktop.org/wayland/weston/commit/903b6b93367e shared/ meson.build signal.c signal.h
11:19wlb: weston Issue #848 opened by Marius Vlad (mvlad) Deprecate fullscreen-shell https://gitlab.freedesktop.org/wayland/weston/-/issues/848 [Fullscreen-shell]
11:38DodoGTA: Is there a way to check what Wayland compositor is being used? I want to work around a compositor bug
11:39kennylevinsen: This is very intentionally not exposed to avoid clients making compositor-specific decisions
11:39pq: No.
14:24wlb: weston Issue #846 closed \o/ (ivi-shell: setting surface visibility to 0 does not prevent the content from being rendered https://gitlab.freedesktop.org/wayland/weston/-/issues/846)
15:14davidre: That window icon thread is beyond saving imo
17:36bwidawsk: What exactly is the purpose of xdg_surface.state.activated? Seems sensible to set it once a buffer is attached (or maybe not?), but when would you unset?
17:38vyivel: bwidawsk: do you mean xdg_toplevel? activated is usually sent when the surface is focused
17:38bwidawsk: yes, I meant toplevel
17:38bwidawsk: vyivel: it clearly states though: `Do not assume this means that the window actually has keyboard or pointer focus.`
17:39vyivel: yes, it's intended to be used to figure out what to draw
17:39emersion: it's for visual feedback
17:39emersion: maybe it's a touch-only device
17:40emersion: in that case, you'd have no "current keyboard focus" for instance
17:40bwidawsk: ok, so when would it be unset?
17:41emersion: when the window is not active :P
17:41emersion: if you have two windows, one is under the other, typically will not have active
17:41bwidawsk: fully occluded you mean?
17:42bwidawsk: in this case I assumed frame callbacks would be sufficient
17:42bwidawsk: but I suppose something else could happen
17:42vyivel: open e.g. two gtk programs side by side
17:42vyivel: focus one of them
17:42vyivel: it will be activated
17:42vyivel: the other one will have less contrast in its titlebar
17:42emersion: not fully occluded
17:43vyivel: it will be not activated
17:46bwidawsk: vyivel: thanks for the concrete example
17:46bwidawsk: emersion: thanks for the explanation
20:25joshs: when calling: xdg_toplevel::set_fullscreen, how do I get a list of object<wl_output>, so I can choose one to set fullscreen?
20:29vyivel: joshs: just like every other global, output globals are sent with wl_registry.bind
21:44ifreund: but if you don't have a strong reason to choose one, just pass null