01:41 wlb: wayland-protocols Issue #215 opened by () ext-foriegn-toplevel-list-v1: add toplevel index/ordering https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/215
07:04 wlb: wayland Issue #501 opened by () bug when shortcuts are registered before release (alt+shift) https://gitlab.freedesktop.org/wayland/wayland/-/issues/501
07:07 wlb: wayland Issue #501 closed \o/ (bug when shortcuts are registered before release (alt+shift) https://gitlab.freedesktop.org/wayland/wayland/-/issues/501)
09:51 Guest4985: hey everyone
09:52 Guest4985: I'm on EndeavourOS with KDE Plasma 6.1.5
09:53 Guest4985: when I use 3-finger gestures to move between desktops it's ok, but when I try to view all the desktops with 4-finger swipe it doesn't react fast enough, so after a 3-finger swipe I have to wait a bit
09:54 Guest4985: journalctl game me this:Sep 30 12:48:49 eos kwin_wayland_wrapper[52031]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
09:54 Guest4985: Is there a way to make Wayland process this gesture faster?
09:55 kennylevinsen: Guest4985: you are not "running wayland", you are running KDE/Kwin - this would be a question for a KDE forum
09:56 kennylevinsen: wayland is just a set of protocols (think HTTP), and this channel is for their development and their use
09:57 Guest4985: kennylevinsen: oh sorry, i was a bit suspicious it might be wrong channel but still had no idea where to go. The only name that was known to me from this output was Wayland lol
09:58 Guest4985: I'll post to kde channel, thank you
09:58 ramblurr: fwiw, "kwin" in that output refers to kwin, the KDE component that is the wayland compositor (i.e., the process that does all the wayland stuff written by the kde folks)
11:35 ericonr: Hey folks :) I was looking at meson's Wayland module, and it didn't work for the case of implementations vendoring protocols
11:36 ericonr: I'm trying to implement that in https://github.com/mesonbuild/meson/pull/13724
11:36 ericonr: But unsure about the best interface for it
11:36 ericonr: Could anyone interested take a look? :)
11:41 kennylevinsen: ericonr: is it correctly understood that this vendor feature requires the meson.build file to be in the same folder as the vendored protocols?
11:42 kennylevinsen: not a big deal, just making sure I understood the search path correctly
11:43 mclasen: ericonr: here is what gtk does for vendored protocols: https://gitlab.gnome.org/GNOME/gtk/-/blob/main/gdk/wayland/meson.build#L158
11:47 ericonr: kennylevinsen: as mentioned in the PR description, yes, but I don't love it
11:50 ericonr: I very much lack understanding of meson internals, so the implementation itself was me shooting stuff at the wall
11:56 ericonr: mclasen: oh lol
11:57 ericonr: So simply skipping find_protocols works
11:57 ericonr: I guess a much simpler PR would be updating the docs
11:57 ericonr: Would you agree?
11:57 ericonr: Thank you for the reference there!
11:58 psykose: haha
12:14 emersion: tbh i feel like manually calling wayland-scanner is simpler
12:29 wlb: weston Issue #957 closed \o/ (May I ask how to retrieve Weston cursor image data from dmabuf? https://gitlab.freedesktop.org/wayland/weston/-/issues/957)
12:31 ericonr: emersion: any reason in particular?
12:34 emersion: doesn't require a particular meson version, isn't unstable, isn't complicated, isn't much more lines of code, clearer what it does under the hood
12:35 emersion:shrug
12:36 emersion: in general not a fan of having to add code in build systems for a particular tool
12:36 emersion: but ymmv
12:48 soreau: I like being able to see what the code is doing too but if the path works well and is simpler to use, people might start using it
12:48 soreau: at least they're making an effort to house common code
12:54 psykose: it's nice seeing what it's doing until you see the exact same thing copied into hundreds of projects :D
12:54 psykose: i guess that's why the gnome module exists
12:54 psykose: and why some people like cmake, since there's external scripts of varying quality you can copy around instead of needing the main build system to add support for $tool
12:56 soreau: cmake's problem is two fold as I see it - 1) if you don't call the correct functions to create a lib it can't be found in nonstandard path 2) s/pkg-config//
12:56 soreau: last time trying to build vulkan into nonstandard prefix was a figt
12:56 soreau: fight*
12:57 soreau: I figure the people that still use cmake haven't bothered to give meson a look
12:58 psykose: a lot of that is mostly due to the combination of 'external .cmake scripts are supported' and its' age paired with the big 3.x reimagining of how you're meant to write cmake
12:58 psykose: so after all this time there are 50 ways to do something, and various things all over the place
12:58 psykose: a centralised implementation is much less likely to fall into that
12:58 Ermine: if you're using qt you're bound to cmake...
12:58 psykose: not really, meson has the qt6 module
12:58 psykose: but it's missing some small things for now that will get added eventually
12:59 Ermine: iirc it's missing some parts
12:59 psykose: qml_module is the biggest one
13:09 wlb: weston Merge request !1619 opened by () desktop-shell: Don't attempt to re-add the view to panel layer https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1619
13:09 ericonr: emersion: yeah, my point is basically psykose's hehe. I don't like to see repeated snippets all over the place
13:10 ericonr: And if I understood it correctly, I think meson likes that people have to go through upstream for new modules, it avoids fragmentation and the implementations can be much better
13:11 ericonr: also, fwiw, doing it the way home does it would only mean a requirement of 0.62.0
13:11 ericonr: s/home/gnome/
13:11 jadahl: ericonr: FWIW, I've avoided it so far due to it being marked as experimental
13:11 jadahl: trying to minimize frustration dealing with stable branches, and using experimental features isn't helping with that
13:11 psykose: rust was unexperimentaled after mesa started making use of it iirc
13:12 psykose: i think if there's nothing to breaking-change on the interface it could just be promoted
13:13 ericonr: https://github.com/mesonbuild/meson/pull/10238
13:13 ericonr: jadahl: it's been experimental for a long while now, every distro has it at this point
13:14 jadahl: maybe time to change that?
13:14 emersion: oh, that
15:20 wlb: weston Merge request !1620 opened by () libweston: Move weston_get_backend_type after enum declaration https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1620
16:59 karenw: Hi, trying to write a simple wayland-egl app. eglMakeCurrent returns EGL_SUCCESS, but I'm not seeing anything on screen other than a tray icon. WAYLAND_DEBUG is showing no wl_buffer ever got attached. I assume I missed a step somewhere?
17:04 soreau: karenw: you might review what happens in weston-simple-egl.c
17:04 soreau: it might be that you need to make a call to set toplevel
17:06 karenw: soreau: Wow. 1) Why did that never come up in my googling for wayland egl examples. 2) Immediately spotted the problem when I looked at eglSwapBuffers in that file. I was passing the wl_surface not the wl_egl_surface.... I has the dumb.
17:09 soreau: weston clients hide in plain sight ;)
21:19 wlb: wayland-protocols Issue #216 opened by () Control keyboard LEDs from a background process https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/216