londoed_ has quit [Remote host closed the connection]
londoed_ has joined #river
groknull has joined #river
groknull has quit [Remote host closed the connection]
groknull has joined #river
groknull has quit [Remote host closed the connection]
adamcstephens has quit [Ping timeout: 276 seconds]
adamcstephens has joined #river
lxsameer has quit [Ping timeout: 272 seconds]
waleee has quit [Ping timeout: 248 seconds]
vaivis has joined #river
vaivis has quit [Read error: Connection reset by peer]
vaivis has joined #river
vaivis has quit [Read error: Connection reset by peer]
vaivis has joined #river
lxsameer has joined #river
vaivis has quit [Read error: Connection reset by peer]
vaivis has joined #river
vaivis has quit [Read error: Connection reset by peer]
snakedye_real has joined #river
snakedye has joined #river
snakedye_real has quit [Client Quit]
<novakane>
there is a thing a bit annoying with hide-cursor timeout, when you have a popup displayed when the cursor hovers over something, the popup is close when the cursor hide
vaivis has joined #river
vaivis has quit [Client Quit]
<tleydxdy[m]>
Conceptually those popups are meant to show when you are "using your mouse" right?
<tleydxdy[m]>
maybe just the timeout is too short?
elshize has quit [Ping timeout: 246 seconds]
elshize has joined #river
<novakane>
yeah I probably should use a timeout a bit longer, but I don't know if it would make sense if the cusor, even hidden, is on a popup it would display it
<novakane>
it is probably counter intuitive though
<ifreund>
Yeah, I don't think a hidden cursor should e.g. cause button hover effects to trigger
<novakane>
yeah it's a bit annoying if this is something that have a lot of text to read but I guess I need to keep my curosr moving above, making some small circle xD
<ifreund>
I'd just use a much longer timeout
<ifreund>
If you see a way to improve river's behavior here without negatively affecting other cases that would of course be welcome though
<tleydxdy[m]>
would be nice if the mouse has a presence sensor XD
<tleydxdy[m]>
idea, what if we made it so the cursor doesn't enter any new surface, but if it is being passed already we keep it that way
<tleydxdy[m]>
probably also need to break the pass through if there is a new layout request since the mouse could end up on a different part of the surface
<tleydxdy[m]>
so we have two attribute, hidden and passthrough, on timeout it only sets hidden, but on operations that could result in cursor landing elsewhere it sets no passthrough (if hidden)
<tleydxdy[m]>
like switching tags, switching outputs, or starting a new layout request
<ifreund>
> I don't think a hidden cursor should e.g. cause button hover effects to trigger
<tleydxdy[m]>
yeah, but if it where hovering above something already and then it gets hidden
<tleydxdy[m]>
This will keep it that way
<tleydxdy[m]>
it's like a delayed no passthrough
<tleydxdy[m]>
like it will not trigger anything new still
<ifreund>
I don't want a button hover effect to continue if the cursor is hidden
<ifreund>
Maybe I didn't say that clearly enough the first time
<tleydxdy[m]>
yeah that's valid
<tleydxdy[m]>
but it's the exact thing novakane was finding right?
<ifreund>
no
<tleydxdy[m]>
> there is a thing a bit annoying with hide-cursor timeout, when you have a popup displayed when the cursor hovers over something, the popup is close when the cursor hide
<tleydxdy[m]>
this?
<ifreund>
ok, yeah I guess that is exactly what I want to happen
<novakane>
e.g on river github page, you hover one of the contributor on the contributors list on the right side, the popup with disapears with the cursor
<ifreund>
I don't think there's anything that we should change here, just use a longer timeout or disable hiding entirely
<novakane>
s/with/will/
<ifreund>
or use hide when typing or whatever
<novakane>
yeah anything else would probably have drawbacks
<tleydxdy[m]>
has to be 4269ms, anything else has problems
<novakane>
I hope you're right or I'll blame you :D
<ifreund>
I guess I need to run pam in a child process for my waylock rewrite, if I block the wayland event loop for too long with a pam library call the server can send enough events to fill up the server side buffer and kill the client :/
<ifreund>
that's pretty dumb
<ifreund>
good news is that since ext-session-lock-v1 is a thing now that bug isn't a security issue!
<ifreund>
I guess I now have a working ext-session-lock-v1 lockscreen in Zig, though it has 0 UX so far
<novakane>
more secure without UX :P
<novakane>
can't be compromised if nobody can unlock it
Guest80 has joined #river
Guest80 has quit [Client Quit]
snakedye has quit [Read error: Connection reset by peer]
snakedye has joined #river
adamcstephens has quit [Ping timeout: 276 seconds]
adamcstephens has joined #river
elshize has quit [Ping timeout: 240 seconds]
elshize has joined #river
vaivis has joined #river
lxsameer has quit [Ping timeout: 240 seconds]
lxsameer has joined #river
<mizzunet>
dnkl the unstable experience of river once yambar was because I accidentally uninstalled libxshmfence.
<mizzunet>
But I see that neither river nor yambar depends on this one.
<ifreund>
that sounds weird
<mizzunet>
Yeah
<mizzunet>
This package with neovide-bin which I later uninstalled and this issue started occuring
<dnkl>
weird, and I have absolutely no idea why libxshmfence matters...
<mizzunet>
s/with/installed with
lxsameer has quit [Ping timeout: 256 seconds]
lxsameer has joined #river
<dnkl>
just noticed that drag operations (drag-to-select text in terminal, drag scrollbar in browser etc) "survives" the view being hidden, and then coming back. For example, via set-focused-tags. Is this intended?
waleee has joined #river
<ifreund>
dnkl: there's a TODO about that, I decided that it was too tricky to implement robustly until we have a scene graph