14:02 wlb: weston/main: Derek Foreman * desktop-shell: check view mappedness in desktop_surface_removed https://gitlab.freedesktop.org/wayland/weston/commit/30fd16dae73f desktop-shell/shell.c
14:02 wlb: weston/main: Derek Foreman * compositor: Unmap views moved to layers outside of the scene graph https://gitlab.freedesktop.org/wayland/weston/commit/003e529d4609 libweston/compositor.c
14:02 wlb: weston Merge request !1592 merged \o/ (compositor: Unmap views moved to layers outside of the scene graph https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1592)
15:43 ykaelig: Hello
15:45 ykaelig: I'm trying to build and install wayland in a non standard path, everythign works fine if I disable the documentation option but if not the program dot is not found, which is also installed in a non standard path. Any idea if Ican resolve this issue ? Thx
15:47 ykaelig: Dot who is in fact a program from graphviz, installed in this non standrad path.
15:47 ykaelig: Maybe I missed some other deps that are needed to find the dot program ?
15:50 ykaelig: It work when graphviz is system wide installed but I want to use my custom path
15:50 ykaelig: Seems t obe an issue with the build system
16:31 ykaelig: re
16:47 Arnavion: It uses meson find_program() to find dot and you can see all the ways to override the path here: https://mesonbuild.com/Reference-manual_functions.html#find_program
16:48 Arnavion: (3) is probably most appropriate for your case
17:52 ykaelig: thanks
17:52 ykaelig: But in wayland there is no path defined for dot. There is a default one in this case ?
17:58 ykaelig: it is not supposed to look at MyPath/usr/bin/ by default ?
19:54 kiilerix: Following up on discussion yesterday to see if someone has other good ideas: How can we reconfigure the new Microsoft Copilot key that sends KEY_LEFTMETA KEY_LEFTSHIFT KEY_F23? Is there a way to configure the input stack (libxkbcommon) to discard these modifiers once it sees F23?
22:01 daniels: libinput rather than libxkbcommon, but yeah
23:20 whot: kiilerix: you can't easily discard modifiers after you see them unless you hold those modifiers back for an unspecified period of time every time
23:20 whot: and that's a no-go for shift
23:21 whot: unless they're guaranteed to arrive in the same frame every time there isn't much we can do that doesn't impact everyone else too. A better approach would be to chance F23 into the right key type so it triggers a new xf86CoPilot keysym and handle it like every other combo