01:26 tommybomb: How do you trigger "wl_keyboard_repeat_info"? I assumed I was supposed to just hold a key, but I think I have misinterpreted it.
01:33 tommybomb: Sorry, ignore me. I figured out it's emmitted once and you take care of the rest.
02:03 wlb: wayland-protocols Issue #132 opened by M. Stoeckl (mstoeckl) fractional-scale-v1: should advise on rounding calculation https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/132
04:24 tommybomb: What is the proper way to close a toplevel surface? Calling the destroy methods doesn't seem to be closing it.
04:28 tommybomb: Nvm, calling the event loop after the destroy calls solved this. If you have anymore information, please let me know. Thanks.
09:31 pq: tommybomb, "calling the event loop" sounds like a suspicious program design if it does not actually mean "return to event loop". You should always return to your event loop ASAP, which then takes care of e.g. flushing Wayland requests out.
09:33 pq: tommybomb, you may also want to schedule work like drawing to be executed only once your event loop is about to sleep, so you don't have pending events that might affect what you want to draw.
18:54 wlb: wayland-protocols Issue #133 opened by simplejack-src (simplejack-src) Add privledge feedback https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/133