ifreund changed the topic of #river to: river - a dynamic tiling wayland compositor - https://github.com/ifreund/river - channel logs: https://freenode.irclog.whitequark.org/river/
travankor has joined #river
leon-p has quit [Quit: leaving]
travankor has quit [Ping timeout: 240 seconds]
waleee-cl has quit [Quit: Connection closed for inactivity]
travankor has joined #river
<dominikh> remember when I complained about having to implement xwayland support? yeah, that's why :P
trav85764 has joined #river
travankor has quit [Ping timeout: 240 seconds]
trav85764 is now known as travankor
exception has joined #river
travankor has quit [Remote host closed the connection]
exception has quit [Ping timeout: 260 seconds]
exception has joined #river
waleee-cl has joined #river
leon-p has joined #river
<ifreund> turns out that it's actually even more annoying than that
<ifreund> I was wrong, I do tell the clients that they've been moved which then causes the code ensuring atomic layout updates/general frame perfection to wait for the next commit before updating things
<ifreund> which doesn't play nicely with how the cursor code currently works
<ifreund> I wonder what bad things happen if you just tell all X11 clients they are always at 0,0
<ifreund> alright well we now just ignore xwayland views in transactions. problem solved
<ifreund> I see no reason to break my current abstractions to try and make xwayland stuff frame-perfect when it probably isn't even possible
<ifreund> also don't want that complexity