ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
agners has quit [Remote host closed the connection]
st3r4g has quit [Read error: Connection reset by peer]
st3r4g has joined #wayland
hendursaga has quit [Remote host closed the connection]
<flibitijibibo>
just ran into something odd with pointer constraints... for pointer_constraints_unstable_v1 is it possible (or more importantly, intended) to set a region in lock_pointer to be screen-relative rather than surface-relative?
hendursaga has joined #wayland
<flibitijibibo>
main motivation is a ClipCursor implementation which is thankfully not relevant to the application for wl, but i did notice the region didn't specify a coordinate system (unless i missed a line) https://github.com/libsdl-org/SDL/pull/4892
<emersion>
no, the region is in surface coords
<emersion>
clients don't know their position on screen anyways
<flibitijibibo>
that's what i figured - i could hypothetically see how a screen-relative constraint could work without broadcasting the window position or anything, but it seemed like a stretch
___nick___ has quit []
<flibitijibibo>
so another function in the pile of "crap i don't need to write"
___nick___ has joined #wayland
ecloud has quit [Ping timeout: 480 seconds]
ecloud has joined #wayland
flibit has joined #wayland
flibitijibibo has quit [Read error: Connection reset by peer]