09:28 <leon-p> i already asked on fedi, but I'll ask here since some riverguile users hang out here as well: I am designing the replacement for riverguile right now. Would you prefer a library offering a (next-event) function with returns ('event-type arg1 arg2 arg3), or something based on hooks? I feel hooks are both more idiomatic scheme and keep things simpler (i.e. lifetime of context object is handled entirely by the library), but I am open for feedback

09:39 <ifreund> hmm, I've never used wayland from a "next-event" style API. It seems like it might be a bit awkward to associate events with wayland objects

09:39 <leon-p> FWIW there won't be a direct correlation to Wayland events. The library has it's own set of events

09:40 <ifreund> ah

09:40 <leon-p> also, Wayland dispatch already is a next-event kind of system, it just happens to call the handler functions for you :)

09:42 <leon-p> object association should be simple in this case at least: they are already associated by the time the library emits anything, so it's just passing pointers to opaque objects

10:03 <LarstiQ> leon-p: I don't know atm but I shall at least start following you on Mastodon to not miss future questions :)

13:16 <nrbrd> hey folks! I've been facing one issue with my new multi-monitor setup, and I'd to know if someone has a fix for that ...

13:17 <nrbrd> I have three monitors setup, and every time I restart my computer, the behavior of "focus-output next" changes

13:17 <nrbrd> which makes me think there is something odd with the ordering ....

13:31 <LarstiQ> in which way? The ordering of the monitors in the list?

16:44 <choucavalier> is it possible to share the workspaces in-between monitors with river? the same way as i3 / sway. i recently tried to give a presentation with pdfpc, where you get the "presentatator screen" and the projected screen. this did not work with river sadly

16:44 <choucavalier> i could not get the usual presentator view on my laptop and the slides on the projector

16:44 <choucavalier> and i think this is due to the way each monitor has its own workspaces / tags in river

17:13 <ifreund> choucavalier: there's nothing stopping pdfpc from working with river

17:13 <ifreund> it opens 2 separate windows and you have to move them each to the correct outputs

17:13 <ifreund> you could probably even add a rule using riverctl to automate the process

17:16 <choucavalier> yeah i guess trying that 2 minutes before giving the lecture was not the optimal way to go about it

17:22 <choucavalier> pdfpc does not work out of the box with river though

17:22 <choucavalier> what's weird is that when i launched it i only got the 'presenter view'

17:22 <choucavalier> i did not have the 2 seperate windows opened you're talking about

17:23 <choucavalier> the one that was supposed to go on the projected screen was missing

17:26 <ifreund> are you sure it wasnt hidden behind the other fullscreen window?

17:27 <ifreund> maybe there's some pdfpc option thats necessary which I'm forgetting about, been a while since Ive used it but it definitely worked in the past