<aelius>
seems like zig recently had some syntax changes, I keep having to install different versions of zig to get bars and such to compile
<aelius>
river 3.9 won't compile with zig 13 but git master will
<aelius>
bleh, dam seems to not work with the river git master :v
<aelius>
testing, brb
<aelius>
initial use shows no crashing nor any sign of that bug,
<aelius>
but the keyboard capture is still absent
<aelius>
I can't send alt-tab to the host, for example, or the Winkey at all
waleee has quit [Remote host closed the connection]
<aelius>
the moonlight shortcut ctrl-shift-alt-s is supposed to bring up stats, but isn't
<aelius>
ctrl-shift-alt-q does end the stream, though. My "mod-f" does toggle moonlight's fullscreen instead of passing it to the host, etc
<aelius>
(that's in my river binds)
Snetry has quit [Ping timeout: 244 seconds]
Snetry has joined #river
schneid3306 has quit [Quit: schneid3306]
<aelius>
spoke too soon. hasn't crashed yet, but the mouse can no longer interact with clients
<aelius>
observation 1: I switched to a different tag while moonlight was fullscreen: and the mouse was missing. I switched moonlight to windowed, switched to a different tag, and the mouse will vanish when it enters the area where moonlight was, even if it is no longer a visible client
<aelius>
it reappears when it leaves that zone
<aelius>
at this point the mouse cannot interact with other clients
<aelius>
exit moonlight, the mouse no longer vanishes, but still cannot interact
<aelius>
keyboard control remains
<aelius>
It seems like this is the result of wayland beliving moonlight owns the mouse cursor, and it SHOULD own the keyboard but doesn't. When river allows me to switch to different tags/clients, some state confusion happens
<aelius>
as an aside, the bug where firefox 137 is too big can be temporarily bypassed by dragging a tab to a different firefox window. seems to re-evaluate its state