Simon Ser

wlr-protocols has migrated to gitlab.freedesktop.org. This issue has been moved to: https://gitlab.freedesktop.org/wlroots/wlr-protocols/-/issues/44

wlr-protocols has migrated to gitlab.freedesktop.org. This pull request has been moved to: https://gitlab.freedesktop.org/wlroots/wlr-protocols/-/merge_requests/106

wlr-protocols has migrated to gitlab.freedesktop.org. This issue has been moved to: https://gitlab.freedesktop.org/wlroots/wlr-protocols/-/issues/95

If wonder if it would be desirable to change this to a ping/pong mechanism [similar to xdg-shell](https://gitlab.freedesktop.org/wayland/wayland-protocols/-/blob/master/stable/xdg-shell/xdg-shell.xml#L92).

>If I understand correctly, this would just make the ability to use this to achieve atomicity of new outputs implicit instead of explicit. Yeah. That would work similarly to `wl_display_roundtrip`:...

Overall looks good. Would be nice to see a client & compositor implementation!

wlr-protocols has migrated to gitlab.freedesktop.org. This pull request has been moved to: https://gitlab.freedesktop.org/wlroots/wlr-protocols/-/merge_requests/86

wlr-protocols has migrated to gitlab.freedesktop.org. This issue has been moved to: https://gitlab.freedesktop.org/wlroots/wlr-protocols/-/issues/50

>But you can fulfill this use-case anyway by just listening for keymaps on wl_seat, right? No, because when you switch the layout, the keymap doesn't change (it contains multiple layouts)....

>people suggested parsing evdev.xml (part of xkeyboard-config) All right. In any case, it doesn't belong to this protocol, and should be done client-side.