06:00 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?
06:19 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
06:26 wlb: wayland Issue #371 opened by yshui (yshui) Clarify the encoding of modifiers/group in wl_keyboard.modifiers https://gitlab.freedesktop.org/wayland/wayland/-/issues/371
06:41 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
06:41 yshui`: but wl_keyboard.enter has all the currently pressed keys? is it not enough for recovering the modifier state?
06:45 whot: yshui`: numlock for example won't be in that list since it's (statistically) never down when you change focus
06:46 yshui`: hmmm, i see.
06:47 whot: same with capslock if it's set up as that
09:32 smallville7123: does wayland deal with *_CONTEXT_RESET_ARB (context reset/loss)
09:34 emersion: the wayland protocol does not
09:55 smallville7123: oki
09:55 smallville7123: as im wondering how desktop apps handle this
10:04 MrCooper: they need to create a new context, which will create new Wayland resources as well
10:06 MrCooper: the more interesting question might be what if it happens to the compositor, see e.g. https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/112
10:15 smallville7123: hmmm
13:46 wlb: weston Issue #732 closed \o/ (Configure mouse button as a combination of keyboard keys https://gitlab.freedesktop.org/wayland/weston/-/issues/732)
17:48 wlb: weston Merge request !1193 opened by Sergio Gómez (SergioGDR) Fix assert for valid confine region https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1193
21:32 wlb: wayland-protocols Issue #136 opened by Dallas Strouse (orowith2os) Desktop image protocol https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/136