ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
davidawesome has quit [Remote host closed the connection]
davidawesome has joined #wayland
Brainium has joined #wayland
alarumbe has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
rasterman has joined #wayland
Drakulix has quit [Remote host closed the connection]
Drakulix has joined #wayland
<Consolatis>
danieldg: I know Giffoni already left but layershell + fully transparent surface with anchor to the screen edge in question + overlay / top layer + no keyboard interactivity should do the trick
<danieldg>
Consolatis: unless there's another layer shell surface along that edge...
<Consolatis>
true. I've experimented with that in the past for a panel auto hide feature, e.g. the actual panel is unmapped and replaced with such a transparent surface and on mouse enter the two are switched again
<danieldg>
plus it'd interfere with grabbing 1-pixel borders of windows for resizing
<vyivel>
there's also a problem of clicks not being passed through
<danieldg>
I believe the windows 95 panel actually showed a 1-2 pixel 'edge' when hidden :)
<Consolatis>
for the 1-pixel borders that could be overcome by leaving that side of the transparent surface out of the input region
<Consolatis>
for the clicks not being passed through I agree, that would be the compromise
user21 has quit [Remote host closed the connection]
<davidawesome>
I mean I dont know how they do it, but I use deskflow for that in wayland, and it has some verry buggy interactions with the screen in the way they did it (its a opensource subproject for the comercial version). It just extends the screens past bounds on all sides, then teleports the mouse constantly if you go outside on a side of the screen you wernt supposed to, instead of the