ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
rv1sr has quit []
lsd|2 has quit [Ping timeout: 480 seconds]
bindu_ has quit [Remote host closed the connection]
bindu has joined #wayland
CodeSpelunker has joined #wayland
CodeSpelunker has quit [Quit: CodeSpelunker]
kabaka has joined #wayland
kabaka is now known as Guest1681
glennk has quit [Ping timeout: 480 seconds]
melnary_ has quit [Read error: Connection reset by peer]
melnary has joined #wayland
atticf has quit [Ping timeout: 480 seconds]
atticf has joined #wayland
atticf has quit [Ping timeout: 480 seconds]
kasper93 has quit [Remote host closed the connection]
atticf has joined #wayland
larunbe has joined #wayland
alarumbe has quit [Read error: No route to host]
Brainium has quit [Quit: Konversation terminated!]
nerdopolis has quit [Ping timeout: 480 seconds]
iomari891 has joined #wayland
mxz_ has joined #wayland
mxz has quit [Ping timeout: 480 seconds]
mxz__ has quit [Ping timeout: 480 seconds]
mxz_ is now known as mxz
kts has joined #wayland
glennk has joined #wayland
Guest1681 has quit [Ping timeout: 480 seconds]
yshui_ has joined #wayland
yshui has quit [Ping timeout: 480 seconds]
kts has quit [Quit: Konversation terminated!]
eroc1990 has joined #wayland
kts has joined #wayland
mxz_ has joined #wayland
kts has quit [Quit: Konversation terminated!]
rv1sr has joined #wayland
kts has joined #wayland
sewn has quit [Remote host closed the connection]
sewn has joined #wayland
<llyyr>
what does xdg_toplevel activated state actually mean? Can I assume this to mean that the window is fully visible and not partially occluded by another window on top?
<llyyr>
my use case is trying to detect when the user wants to drag the window or bring it to front by left clicking, instead of left clicking to trigger some keybind in the application
<llyyr>
detecting keyboard/pointer focus works in some situations, but doesn't on focus-follows-cursor compositors where the window will get keyboard and pointer focus as soon as the cursor enters the window
<vyivel>
"Can I assume this to mean that the window is fully visible and not partially occluded by another window on top?" no, a compositor may have multiple window layers (e.g. tiled/floating/always-on-top)
<llyyr>
does any protocol provide any information to communicate user information in this case?
<llyyr>
user intention*
<llyyr>
whether they want to bring a window to the front or actually do whatever left click does in the application
<vyivel>
the use case sounds strange to me, if i left click on a ui element in window i expect it to be triggered
<vyivel>
"bringing a window to the front" is completely out of the application's scope, it's something only the compositor manages and should know about
<llyyr>
the use case is mpv and seeing if it's possible to bind pause to left click, it'd be very annoying if mpv cycled pause everytime the user clicked on it to bring it to the front of the stack
<llyyr>
I see that it's not possible then
<vyivel>
i'd personally find it very annoying if i clicked on non-top-of-the-stack mpv and it didn't pause tbh
<llyyr>
some users find it annoying the other way around, which is why it's bound to right click atm but we're trying to free up right click for a context menu :D
<vyivel>
because that's not how every other program works
kts has quit [Quit: Konversation terminated!]
mriesch_ has joined #wayland
V has quit [Remote host closed the connection]
kode546 has quit []
mriesch has quit [Ping timeout: 480 seconds]
kode546 has joined #wayland
V has joined #wayland
mriesch_ has quit []
mriesch has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
coldfeet has joined #wayland
Sid127 has joined #wayland
chiku has quit [Ping timeout: 480 seconds]
kts has joined #wayland
kts has quit []
<emersion>
I'd say this is better left as compositor policy
<emersion>
compositor can intercept the left click event and not relay it if desirable