ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
privacy has joined #wayland
cstub has quit []
nielsdg has joined #wayland
akallabeth[m] has joined #wayland
YaLTeR[m] has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
cmeissl[m] has joined #wayland
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
dryya has joined #wayland
<dryya>
qQ$L`=AJp@@L<ZH!9uTAga=yt
niecoinny[m] has joined #wayland
nerdopolis has joined #wayland
zvarde198830320677919168 has joined #wayland
floof58 has quit [Ping timeout: 480 seconds]
dryya has quit [Quit: Page closed]
floof58 has joined #wayland
ttancos[m] has joined #wayland
fmuellner_ has quit [Ping timeout: 480 seconds]
privacy_ has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
privacy has quit [Ping timeout: 480 seconds]
i509vcb has quit [Quit: Connection closed for inactivity]
privacy_ has quit []
dani-g5x[m] has joined #wayland
go4godvin has joined #wayland
go4godvin is now known as Guest172
Coelacanthus[m] has joined #wayland
zhxt[m] has joined #wayland
q234rty[m][m] has joined #wayland
<clamps>
< dryya> qQ$L`=AJp@@L<ZH!9uTAga=yt <- been a while since i've seen line noise, reminds me of my youth
<ascent12>
You have to bind to zxdg_output_manager_v1 and use get_xdg_output to see the events
fmuellner has joined #wayland
<d_ed[m]>
Qt will use xdg_output if available
<d_ed[m]>
as for rotation
<heeen>
The QWaylandXdgOutputManagerV1 extension provides a way for a compositor to describe outputs in a way that is more in line with the concept of an output on desktop oriented systems.
<heeen>
Some information may not make sense in other applications such as IVI systems.
<heeen>
hmm
<heeen>
my application is more like an embedded/ivi system than desktop
privacy has joined #wayland
abeltramo58959 has joined #wayland
abeltramo5895 has quit [Remote host closed the connection]
<pq>
If clients are allowed to warp a pointer within their (exposed input region?) window area while having pointer focus, should we worry about e.g. malicious web code taking the pointer hostage by forcefully keeping it in the window?
<dottedmag>
Do browsers provide API to warp pointers?
<pq>
I don't know.
cstub has joined #wayland
<pq>
I might not worry about locally installed software. What about flatpak et al.?
<pq>
just thinking about worst case scenarios, are they significant enough to care about
<pq>
requiring a valid input serial might even be all that's needed
<vsyrjala>
does pointer warping have actual use cases (apart from x11 legacy)?
<pq>
yeah (discussed in the backlog), even if niche
<davidre>
pq: Keeping the cursor in the window: Doesnt the same worry apply to confinement and locked pointers?
<pq>
They should already have escape hatches in compositors.
<davidre>
I would escape that then warping would as well :)
<davidre>
*expect
<pq>
sure
<pq>
but then I don't think warping can be just one request to move to x,y that either works or not, would it not need feedback whether it actually did?
<pq>
or perhaps something like warping enabled/disabled events, so the client knows what's possible and can adapt UX
<zamundaaa[m]>
Dallas Strouse (she/her) 🧑🏫: you need to authenticate with NickServ again. Your messages aren't reaching IRC
<zamundaaa[m]>
pq: that sounds racy
<pq>
in some sense, it cannot be race-free, right?
<davidre>
pointer constraints has locked/unlocked, confined/unconfined signals currently
<pq>
that's actually a good point, how does the client know where the pointer is after a warp request and without the end user moving the pointer
<pq>
would there be a pointer focus leave+enter pair? but what if buttons are down?
<davidre>
pq: You could make it so that if a compositor deemed the warp request acceptable it would just respond as normal with wl_pointer::motion, client side there would only be one path for cursor position then
<davidre>
If the compositor doesnt allow it there would just be no motion event
<davidre>
I guess it could be a bit ambigious especially if there are buttons held by a user and things being async
<davidre>
maybe just a pointer_warped(x, y, surface) response by the compositor?
<pq>
wl_pointer.motion is not meant for such "software actions" though and might break the timestamp ordering
<pq>
pointer_warped event could make a lot of sense I guess
<pq>
it would allow compositors to warp pointers at will without the awkward pointer focus leave+enter cycle which just doesn't work if buttons are down, since we have no events defined for entering with buttons already held
<pq>
one source of compositor-side pointer warp is moving the window underneath the pointer
nerdopolis has quit [Ping timeout: 480 seconds]
<davidre>
pq Of course it would only work if the client has the new global bound (or object created?) for these not client used usecases
<davidre>
Or are you thinking of adding such an event to wl_pointer
ukiran has quit [Ping timeout: 480 seconds]
kts has joined #wayland
rv1sr has joined #wayland
kts has quit [Ping timeout: 480 seconds]
ukiran has joined #wayland
Moprius has joined #wayland
Guest140 is now known as ForeverNoob[m]
iomari891 has quit [Ping timeout: 480 seconds]
<pq>
davidre, the same problem still even if in wl_pointer, there would be clients who bind an older version.
<davidre>
I would guess clients supporting a newer wl_pointer is more likely then implementing a new pointer warp protocol just so compositor authors have it easier ;)
<zamundaaa[m]>
pq: wl_pointer.motion is already used for this purpose though, in pointer constraints
Cyrinux9474 has quit []
Cyrinux9474 has joined #wayland
<pq>
ugh
rv1sr has quit []
sevz has quit [Quit: WeeChat 4.0.4]
nerdopolis has joined #wayland
Moprius has quit [Quit: bye]
pochu has quit [Ping timeout: 480 seconds]
iomari891 has joined #wayland
lbia has quit [Quit: lbia]
cstub has quit [Read error: Connection reset by peer]
junaid has quit [Remote host closed the connection]
<orowith2os[m]>
<zamundaaa[m]> "Dallas Strouse (she/her) 🧑🏫: yo..." <- I might as well just write my own IRC/Matrix client for how much this thing breaks
<orowith2os[m]>
holy crap
nerdopolis has quit [Ping timeout: 480 seconds]
iomari891 has quit [Remote host closed the connection]
mainiomano has joined #wayland
mblenc has quit [Ping timeout: 480 seconds]
mblenc has joined #wayland
mblenc1 has joined #wayland
mvlad has joined #wayland
mblenc has quit [Ping timeout: 480 seconds]
mblenc has joined #wayland
mblenc1 has quit [Ping timeout: 480 seconds]
cstub has joined #wayland
mblenc has quit [Ping timeout: 480 seconds]
sima has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
mblenc has joined #wayland
junaid has quit [Remote host closed the connection]
mblenc1 has joined #wayland
junaid has joined #wayland
Moprius has quit [Quit: bye]
mblenc has quit [Ping timeout: 480 seconds]
brian[m]1234 has joined #wayland
brian[m]1234 has left #wayland [#wayland]
mblenc has joined #wayland
nerdopolis has joined #wayland
mblenc1 has quit [Ping timeout: 480 seconds]
Guest236 has joined #wayland
xantoz has joined #wayland
cstub has quit []
mvlad has quit [Remote host closed the connection]
nerdopolis has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
sevz has joined #wayland
mblenc1 has joined #wayland
mblenc has quit [Ping timeout: 480 seconds]
cvmn has quit [Remote host closed the connection]
caveman has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
rasterman has quit [Quit: Gettin' stinky!]
junaid has quit [Remote host closed the connection]