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
bodiccea has quit [Remote host closed the connection]
bodiccea has joined #wayland
wb9688 has quit [Ping timeout: 480 seconds]
ppascher has joined #wayland
wb9688 has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
sozuba has joined #wayland
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
ahartmetz has quit [Quit: Konversation terminated!]
heartburn has joined #wayland
heartburn has left #wayland [#wayland]
Brainium has quit [Quit: Konversation terminated!]
AJ_Z0 has quit [Remote host closed the connection]
AJ_Z0 has joined #wayland
pieguy128 has joined #wayland
flibitijibibo has joined #wayland
doppo has quit [Remote host closed the connection]
doppo has joined #wayland
tent405 has quit [Remote host closed the connection]
tent405 has joined #wayland
pochu has joined #wayland
smallville7123 has joined #wayland
kts has quit [Quit: Leaving]
Sachiel has quit [Ping timeout: 480 seconds]
agd5f has joined #wayland
agd5f_ has quit [Ping timeout: 480 seconds]
<pq>
bl4ckb0ne, it doesn't matter and long as all those resources are from the same client as wl_client. Use what e.g. leads to shorter code. Or if the code is related to operating on a specific resource, then post on the resource.
<pq>
*as long as
kts has joined #wayland
Sachiel has joined #wayland
MajorBiscuit has joined #wayland
mvlad has joined #wayland
ahartmetz has joined #wayland
MajorBiscuit has quit [Ping timeout: 480 seconds]
agd5f_ has joined #wayland
agd5f has quit [Ping timeout: 480 seconds]
smallville7123 has quit [Quit: Konversation terminated!]
mokee has quit [Remote host closed the connection]
manuel1985 has quit [Ping timeout: 480 seconds]
manuel1985 has joined #wayland
molinari has joined #wayland
Cyrinux has quit [Remote host closed the connection]
Company has joined #wayland
manuel_ has joined #wayland
manuel1985 has quit [Ping timeout: 480 seconds]
caveman has quit [Quit: rebooting]
alarumbe has joined #wayland
sozuba has joined #wayland
riverdc has quit []
riverdc has joined #wayland
kts has quit [Quit: Leaving]
caveman has joined #wayland
devilhorns has quit []
kts has joined #wayland
rv1sr has joined #wayland
agd5f_ has quit [Read error: No route to host]
agd5f has joined #wayland
Vanfanel has joined #wayland
<Vanfanel>
In Weston, in desktop-shell/shell.c, how would I simulate that a fullscreen window is clicked? I'm trying with "shsurf->view->click_to_activate_serial = surface->compositor->activate_serial;", but it doesn't work.
<Vanfanel>
pq: Can you please give any ideas here?
<Vanfanel>
My goal here is that fullscreen windows always pass the tests in maybe_enable_pointer_constraint()
<kennylevinsen>
if it's a local modification anyway, why not just modify the checks themselves?
<Vanfanel>
kennylevinsen: The idea is startck hacking around in order to get a real change in Weston so fullscreen windows get pointer confinement when created, as it happens on other compositors like Sway