Den4ikRus has quit [Remote host closed the connection]
Den4ikRus has joined #river
angry_vincent has quit [Ping timeout: 245 seconds]
alexherbo2 has quit [Remote host closed the connection]
waleee has joined #river
waleee has quit [Ping timeout: 252 seconds]
mtm has quit [Ping timeout: 252 seconds]
mtm has joined #river
alexherbo2 has joined #river
leopoldek has joined #river
leopoldek has quit [Remote host closed the connection]
tiosgz has joined #river
<tiosgz>
whoops, i hope if has notifications off. didn't really expect today would be another of my think-aloud days...
<leon-p>
tiosgz: regarding your comment: focus-follows-cursor will be WM policy. Both pointer_enter and pointer_motion could trigger it and some WMs may also want to check if a focusable thing is under the cursor after each set_position
<leon-p>
or am I missing your point?
<leon-p>
hmm... I am not too happy with the pointer_motion event, because it makes the update event, which is already where all interesting logic sits, into a hot path, especially for high poll rate pointing devices. But I also see no alternative for the "always" policy of focus-follows-cursor we offer right now
<tiosgz>
leon-p: my point is that the pointer enters the window and is moved, but the former example makes no distinction between the window being moved under the pointer (which doesn't trigger ffc in normal mode)...
<tiosgz>
...and the pointer entering it just after the window was moved (which should trigger ffc)
<tiosgz>
aahh, now i'm back to thinking about actually simultaneous events. expect me getting totally confused and later coming back with the conclusion that the protocol is actually indeed okay
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #river
<tiosgz>
so either i've finally wrapped my head around it and the proto is ok (in which case i've edited the comment in the PR), or i'm irreversibly confused and need to find less difficult things to think about
<leon-p>
now I for my part have accepted that both the thing I am trying to understand is OK /and/ that I am confused and probably should just go out with my friends instead
<leon-p>
what was keeping me up the last few days is thinking about which things really need double buffering on the WM side. I decided to just double buffer everything for now and later simplify the things that don't need it
tiosgz has quit [Quit: nyaa~]
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #river
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #river
angry_vincent has joined #river
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #river
alexherbo2 has quit [Remote host closed the connection]