ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
Brainium has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
alatiera has quit [Ping timeout: 480 seconds]
Leopold has quit [Remote host closed the connection]
Leopold has joined #wayland
DragoonAethis has quit [Quit: hej-hej!]
DragoonAethis has joined #wayland
Brainium has quit [Ping timeout: 480 seconds]
alatiera has joined #wayland
Company has quit [Quit: Leaving]
gfxstrand has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
gfxstrand has joined #wayland
gfxstrand has quit [Remote host closed the connection]
gilvbp has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
tjaden has joined #wayland
cool110 has quit [Quit: ZNC 1.8.2+deb3build2 - https://znc.in]
<riteo>
I need your help here because I can't find anything satisfactory. Should I worry about globals appearing and disappearing in real time? Also, should I delete all "child" objects created by a now-removed global?
bindu has joined #wayland
<riteo>
The thing becomes annoying when I have a list of seat data and I have to iterate it all at every seat-related thing. Perhaps I shouldn't care about aknowledging every single seat?
<riteo>
I'm in a position to either overengineer handling for the removal of globals that should _usually_ stay or ignore it outright. If a specification doesn't say anything regarding something the compositor may do anything pretty much.
<riteo>
...just noticed that in the ticket linked above someone says that if clients have indeed done that we can't rollback. I guess I'll have just to deal with it?
kts has quit [Quit: Leaving]
IndiumInLCD has joined #wayland
IndiumInLCD has quit [Remote host closed the connection]