<ifreund>
novakane: zig-wayland now generates wl_proxy_destroy() wrappers if there is no destroy request for the interface :)
snakedye has quit [Read error: Connection reset by peer]
snakedye has joined #river
sjtio has quit [Quit: Bridge terminating on SIGTERM]
priner has quit [Quit: Bridge terminating on SIGTERM]
edrex[m] has quit [Quit: Bridge terminating on SIGTERM]
pedrohlc[m] has quit [Quit: Bridge terminating on SIGTERM]
anubhavkini has quit [Quit: Bridge terminating on SIGTERM]
voroskoi[m] has quit [Quit: Bridge terminating on SIGTERM]
entenel has quit [Quit: Bridge terminating on SIGTERM]
msiedlaczekelshi has quit [Quit: Bridge terminating on SIGTERM]
<novakane>
ifreund: ah nice! thanks!
<novakane>
I will be less confused :P
sjtio has joined #river
priner has joined #river
voroskoi[m] has joined #river
anubhavkini has joined #river
edrex[m] has joined #river
pedrohlc[m] has joined #river
entenel has joined #river
msiedlaczekelshi has joined #river
snakedye has quit [Ping timeout: 268 seconds]
snakedye has joined #river
waleee has joined #river
<leon-p>
so I tested around with that Xwayland issue where some windows don't receive (or just don't handle?) pointer input when the output is not at position 0,0
<leon-p>
I can confidently say that a properly written X client does not have this issue.
<leon-p>
thse clients must be doing something very weird, maybe with child windows, which I simply can't reproduce
leon-p has quit [Remote host closed the connection]
leon-p has joined #river
<leon-p>
however, as I just experienced, I can crash river if I try to start an X client (xev) when the output is at 10000,10000
<leon-p>
anyway, I'll poke around at it a bit more
<novakane>
could just remove xwayland support, no more problem :P
<leon-p>
tempting
<novakane>
yeah it'll be great once it be possible
<leon-p>
I am already there, everything I need has wayland support