11:55 <maralorn> Hey there, it is my understanding that I can only my full screen at the moment. Does anyone know any dirty hacks how I can achieve sharing only one presentation?

12:06 <p00f> move your presentation to a new tag?

12:09 <maralorn> I guess then I can’t see the people watching the presentation.

12:10 <maralorn> Also my screen has the completely wrong resolution to transfer it whole.

14:19 <LarstiQ> doesn't window/screen sharing depend on the application doing the sharing?

14:30 <maralorn> LarstiQ: There is some kind of API that wayland supports. firefox or obs can request the image from the wayland server. The current implementation for (all?) wl-roots based wayland servers only offers the whole screen to the application which wants to capture, not individual applications or e.g. tags/workspaces.

14:38 <dagle> The screencast portal lets you select an area of the screen.

14:38 <maralorn> dagle: Which software is that?

14:39 <maralorn> Oh, I can configure xdg-desktop-portal-wlr?

14:40 <dagle> xdg-desktop-portal-wlr uses grim to let you select a part of your screen.

14:40 <maralorn> That didn’t seem to happen, when I just used it.

14:41 <dagle> Do you have grim installed?

14:41 <maralorn> Are you maybe confusing grim and slurp?

14:41 <maralorn> But I have both of them installed.

14:42 <dagle> Yeah, I meant slurp. It uses grim too but for the actual screenshot.

14:42 <maralorn> But anyway. Knowing that this is supposed to be a working feature is good to know. Thank you.

14:52 <maralorn> My impression is that the nixos default config for xdg-desktop-portal-wlr does not use slurp.

14:57 <maralorn> Huh, no. The default should be to use slurp. When I start the screen capture I see it flicker for a second but then I somehow don’t see the usual slurp overlay.

14:57 <maralorn> Wondering if anything else is messing with it.

15:13 <LarstiQ> dagle: arbitrary regions? I should try that

15:15 <LarstiQ> usually I just pick my whole laptop screen and use the other monitors for unshared windows

17:27 <Tekk> ifreund: since you're around: do you know of any projects that're using zig-wlroots through the package manager?

22:46 <ifreund> Tekk: no I don't, I haven't tried to get it working myself either. I can't really use the zig package manager for river until https://github.com/ziglang/zig/issues/14281 is solved

22:48 <ifreund> If one doesn't care about their project being packaged by distros it should probably work somehow, what error are you getting?

23:36 <Tekk> ifreund: I was having issues with it saying that there was no such dependency after I minimally modified it from a project I have that uses zap. I wasn't sure if there was something the library I was copying had to do (like add a zig.zon with a version and name)

23:36 <Tekk> Lemme re-paste

23:37 <Tekk> http://paste.debian.net/1304457/

23:38 <Tekk> build.zig is as generated by init-exe, just added some of that as context

23:43 <waleee> Tekk: did the error specifically say that zig-wlroots was missing?

23:44 <waleee> and not eg "wayland"

23:44 <Tekk> no dependency named 'wlroots' in '/home/danny/src/dcc/build.zig.zon'. All packages used in build.zig must be declared in this file

23:45 <waleee> Tekk: what whould the module possibly be called if the repo is named zig-wlroots?

23:46 <Tekk> It's complaining about the wlroots, which is why I thought it might've been that zig-wlroots doesn't export its name.

23:46 <Tekk> changing the dependency name to zig-wlroots changes nothing

23:47 <Tekk> I also verified in my zap project that I'm allowed to name the dependency whatever I want so long as b.dependency and the zon match. I *think* there's something it doesn't like about the download itself

23:53 <waleee> Tekk: which version of zig are you using?

23:54 <waleee> 0.11? or a master build?

23:54 <Tekk> 0.11

23:55 <Tekk> Also to be clear I'm way open to "This isn't a river issue, go bother zig" I'm genuinely not sure