01:15 kestrel: how can i set custom acceleration profile for touchpad on wayland? absolutely no information is available on google
01:57 FreeFull: kestrel: It depends on which compositor you're using
01:57 FreeFull: Although I don't know if libinput even supports non-preset acceleration profiles
02:11 cwegener: Custom acceleration profiles have been introduced in 1.23
02:12 cwegener: Peter's article about it: http://who-t.blogspot.com/2023/01/libinput-and-custom-pointer.html
02:14 cwegener: Relevant mutter issue: https://gitlab.gnome.org/GNOME/mutter/-/issues/2971
05:44 kestrel: cwegener is it possible to enable it on wayland? xinput works only on x11
05:47 cwegener: Only GNOME/mutter have an open issue regarding the implementation of custom acceleration profiles. I have not seen it discussed on the bug trackers of any other compositors.
05:52 cwegener: To clarify - "enabling it on wayland" means that your specific wayland compositor needs to implement the new custom profiles libinput API. And then you need a way to manage the configuration of the custom profile.
05:56 kestrel: so there is no way for me to use it if my compositor, kwin_wayland, does not support it
05:56 kestrel: sounds like a rather backwards way of doing things, deferring this responsibility to each compositor to develop independently rather than a unified solution
10:32 wlb: weston/main: Michael Olbrich * drm-backend: limit reset/restart to output of a failed commit https://gitlab.freedesktop.org/wayland/weston/commit/f843ba34d1f4 libweston/backend-drm/drm.c
10:32 wlb: weston Merge request !1556 merged \o/ (drm-backend: limit reset/restart to output of a failed commit https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1556)
11:20 wlb: weston Merge request !1558 opened by Daniel Stone (daniels) doc: Tie Sphinx -W to Werror configuration https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1558 [Build system], [Documentation]
11:28 Zeroine: Hi everyone, I know this a bit long but I've managed to write a client application that just displays a 400x400 white square. I'm stuck at figuring out why the simple infinite event loop with wl_display_dispatch works but not the one which reads the events manually with the wayland provided functions and uses wl_display_dispatch pending, it should be pretty much the same as the 1st
11:28 Zeroine: one but exit after 5 seconds and do all the cleanup. Here is both the code, a Makefile and the output of WAYLAND_DEBUG=1 for both runs using each event loop https://bpa.st/IZCQ
11:30 Zeroine: If anyone has any advice about code quality, besides the use of globals which I use just for testing, I'd like to hear that as well.
11:30 Zeroine: Oh and also the shm object that gets created has a static name for now, so you need to clean it up in /dev/shm/wlc_shm on Linux.
11:33 daniels: Zeroine: you're missing wl_display_flush() before you sleep, so the compositor never sees your commit
11:33 Zeroine: aah, right
11:38 Zeroine: daniels: now I can receive and handle the wm_base::ping and xdg_surface::configure but it's still not showing the window
11:39 Zeroine: ah nevermind, I forgot to add it in the actual event loop as well
11:39 Zeroine: thanks
11:46 daniels: np
17:51 wlb: weston Issue #917 closed \o/ (13.0.2: documentation build fails https://gitlab.freedesktop.org/wayland/weston/-/issues/917)
17:51 wlb: weston/main: Daniel Stone * doc: Tie Sphinx -W to Werror configuration https://gitlab.freedesktop.org/wayland/weston/commit/de669aeb6094 doc/sphinx/ meson.build run_doxygen_sphinx.sh.in
17:51 wlb: weston Merge request !1558 merged \o/ (doc: Tie Sphinx -W to Werror configuration https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1558)
20:48 wlb: wayland Merge request !400 opened by Caitlyn Stewart (caitcatdev) Changed wl_global, wl_interface and wl_resource to use a uint32_t version in line with protocol documentation. https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/400
20:55 WhyNotHugo: Can a compositor inform a client "there is a notch-like area at a wl_surface at x,y,w,h"?
20:57 WhyNotHugo: Non rectangular output are not a thing, right? Some phones/laptops have screen edges missing too.
20:59 kennylevinsen: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/87