10:29 pq: bl4ckb0ne, yeah, I got the same vibe: "everyone uses threads already anyway".
15:05 bl4ckb0ne: fun times ahead
15:05 bl4ckb0ne: already pulling my hair with multithreaded egl
17:49 wlb: wayland-protocols Issue #128 opened by Simon Ser (emersion) xdg-shell: ack_configure with unmapped surface https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/128 [xdg-shell]
19:47 bl4ckb0ne: what's the difference between wl_client_post_no_memory and wl_resource_post_no_memory
19:50 zmike: one is for clients and the other is for resources?
19:51 bl4ckb0ne: yeah but which one is to be used in which case
19:53 ifreund: they both do the same thing, whichever is more convenient should be used
19:55 Vanfanel: Hi. I have been trying that fullscreen windows always pass the tests in maybe_enable_pointer_constraint(), so they get pointer confinement automatically.
19:55 Vanfanel: To do that, I have been trying to simulate a click on the windows when they are made into fullscreen
19:56 Vanfanel: Any idea on how to do that? I have been trying for a long time already, some ideas are welcome
19:57 Vanfanel: pq suggested that I could add the simulated click in desktop-shell/shell.c
19:58 Vanfanel: But where? I tried adding it in set_fullscreen(), like this: view->click_to_activate_serial = surface->compositor->activate_serial;
19:58 Vanfanel: Sadly that doesn't work. Any ideas, please?
20:03 Vanfanel: Does making "view->click_to_activate_serial = surface->compositor->activate_serial
20:03 Vanfanel: make any sense?
20:08 Vanfanel: ^Forgot to mention that is on Weston!
20:26 bl4ckb0ne: ifreund: but which is is to be prefered when
20:26 bl4ckb0ne: theres a lot of handler funcs that have both client and resource
22:56 wlb: wayland Merge request !289 opened by Simon Ser (emersion) server: avoid zero global name on overflow https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/289 [IPC library]