mon_aaraj has quit [Read error: Connection reset by peer]
mon_aaraj has joined #river
dbuckley has quit [Ping timeout: 240 seconds]
dbuckley has joined #river
vaivis has quit [Ping timeout: 250 seconds]
dbuckley has quit [Ping timeout: 240 seconds]
dbuckley has joined #river
notzmv has joined #river
snakedye_real has joined #river
aXie has joined #river
<aXie>
!seen river
snakedye_real has quit [Remote host closed the connection]
Guest26 has joined #river
omni_ is now known as omni
snakedye_real has joined #river
snakedye_real has quit [Client Quit]
mon_aaraj has quit [Ping timeout: 240 seconds]
mon_aaraj has joined #river
Guest26 has quit [Quit: Client closed]
pkap has quit [Quit: Client closed]
notzmv has quit [Read error: Connection reset by peer]
waleee has joined #river
mon_aaraj has quit [Ping timeout: 250 seconds]
mon_aaraj has joined #river
mon_aaraj has quit [Ping timeout: 248 seconds]
mon_aaraj has joined #river
mon_aaraj has quit [Ping timeout: 246 seconds]
mon_aaraj has joined #river
<leon-p>
hmm... I think something in the cursor movement code is broken. Sometimes the cursor moves to fast when moving a window while the window itself moves correctly. We had this before with clients that do odd thinks when resizing, but now I get it with well behaving clients as well
<leon-p>
but only somtimes. It just randomly appears and then affects all views in the session from then on
<leon-p>
resizing is not affected though.
<leon-p>
only moving
<ifreund>
leon-p: Hmm, I haven't noticed anything like that myself, but then again I almost never move/resize floating windows
<leon-p>
I don't really have the time to investigate right now, but I'll look into it this weekend.
aXie has quit []
elshize has quit [Ping timeout: 256 seconds]
elshize has joined #river
snakedye_real has joined #river
notzmv has joined #river
lxsameer has quit [Ping timeout: 248 seconds]
notzmv has quit [Ping timeout: 240 seconds]
mattnite_ has joined #river
mattnite_ has quit [Client Quit]
mattnite has joined #river
<mon_aaraj>
Hmmm, I wonder.. I'm fairly new to Wayland, having used it only for half a year by now I believe. I sort of wish to try to get rounded window borders somehow working, maybe by making something on top of river or that works alognside it rather than patching river itself, but it seems like generally the viewpoint of it is that it's not possible as of right now to create something on top of wayland
<mon_aaraj>
compositors to manage it, is there? Like some sort of extension to the compositor?
<leon-p>
mon_aaraj: no, you can't add things like rounded corners without touching rivers code
<mon_aaraj>
ah, alright, thank you very much!
<leon-p>
I don't think it would be very practical even if it workds. It would basically just be a recreation of how compositors work on X, meaning you're usually a frame behind and definitely wasting a few cycles.
<leon-p>
a better design would be to add a mechanism that allows river to load user-written shaders, but that is non-trivial
<mon_aaraj>
yep, that's what i've seen given more thought in sway