03:31wlb: wayland-protocols Issue #129 opened by Nick Yamane (nickdiego) xdg-activation: clarify what surfaces are expected as requestor of activation https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/129
07:54ifreund: bl4ckb0ne: it literally doesn't matter which one you call if the resource belongs to the client, have a peek at the source code if you like
08:42pq: bl4ckb0ne, it doesn't matter and long as all those resources are from the same client as wl_client. Use what e.g. leads to shorter code. Or if the code is related to operating on a specific resource, then post on the resource.
08:42pq: *as long as
10:59wlb: wayland/main: Simon Ser * server: fail on global name overflow https://gitlab.freedesktop.org/wayland/wayland/commit/be31c5a8c852 src/wayland-server.c
10:59wlb: wayland/main: Simon Ser * server: rename wl_display.id to next_global_name https://gitlab.freedesktop.org/wayland/wayland/commit/83e9c9e117ac src/wayland-server.c
10:59wlb: wayland Merge request !289 merged \o/ (server: fail on global name overflow https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/289)
15:51Vanfanel: In Weston, in desktop-shell/shell.c, how would I simulate that a fullscreen window is clicked? I'm trying with "shsurf->view->click_to_activate_serial = surface->compositor->activate_serial;", but it doesn't work.
15:52Vanfanel: pq: Can you please give any ideas here?
15:54Vanfanel: My goal here is that fullscreen windows always pass the tests in maybe_enable_pointer_constraint()
16:00kennylevinsen: if it's a local modification anyway, why not just modify the checks themselves?
16:03Vanfanel: kennylevinsen: The idea is startck hacking around in order to get a real change in Weston so fullscreen windows get pointer confinement when created, as it happens on other compositors like Sway
16:04Vanfanel: In fact, I am trying to get a fix for this issue I opened: https://gitlab.freedesktop.org/wayland/weston/-/issues/667
16:05Vanfanel: I am willing to do it myself, but I need a little help here :P