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
ybogdano has quit [Ping timeout: 480 seconds]
ovf has joined #wayland
doppo has quit [Remote host closed the connection]
genpaku has quit [Remote host closed the connection]
cool110 has quit [Remote host closed the connection]
cool110 has joined #wayland
Dami_Lu has quit [Remote host closed the connection]
luyn has quit [Remote host closed the connection]
Dami_Lu has joined #wayland
cool110_ has joined #wayland
cool110 has quit [Remote host closed the connection]
godvino has joined #wayland
Company has quit [Quit: Leaving]
tzimmermann has joined #wayland
godvino has quit [Read error: Connection reset by peer]
lockywolf_ has quit []
dcz has joined #wayland
lockywolf has joined #wayland
<yshui`>
wl_keyboard sends key map and raw key code, is that not enough for the client to support modifiers? why do we need a separate modifiers event?
danvet has joined #wayland
<yshui`>
also how's modifier state encoded in the modifiers event? is it "whatever returned by `xkb_state_serialize_mods`"? it's unclear from the spec
<whot>
yshui`: modifiers may have changed while you weren't looking, so the modifier event notifies you of the *current* state once you get the focus back
<yshui`>
but wl_keyboard.enter has all the currently pressed keys? is it not enough for recovering the modifier state?
<whot>
yshui`: numlock for example won't be in that list since it's (statistically) never down when you change focus
<yshui`>
hmmm, i see.
<whot>
same with capslock if it's set up as that
mvlad has joined #wayland
kts has joined #wayland
Szadek has quit [Ping timeout: 480 seconds]
godvino has joined #wayland
rasterman has joined #wayland
pochu has joined #wayland
godvino has quit [Quit: WeeChat 3.6]
alatiera has quit [Ping timeout: 480 seconds]
molinari has joined #wayland
smallville7123 has joined #wayland
<smallville7123>
does wayland deal with *_CONTEXT_RESET_ARB (context reset/loss)
<emersion>
the wayland protocol does not
<smallville7123>
oki
<smallville7123>
as im wondering how desktop apps handle this
<MrCooper>
they need to create a new context, which will create new Wayland resources as well