On client side the newer wl_keyboard_release is used which is a
destructor call. On server side the shared destroy callback is used
and it's ensured that KWayland doesn't crash if called into the
KeyboardInterface between unbound and destroyed.
Details
Details
- Reviewers
sebas - Group Reviewers
Plasma on Wayland - Commits
- R127:788d21b9543a: Properly handle destroying a Keyboard resource
Test case extended to cover the condition of an unbound
KeyboardInterface.
Diff Detail
Diff Detail
- Repository
- R127 KWayland
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
src/server/keyboard_interface.cpp | ||
---|---|---|
186 | sidenote: should it warn about a version mismatch to help debugging problems with clients, or would this be ineffective here or produce too much noise? |
src/server/keyboard_interface.cpp | ||
---|---|---|
186 | version mismatch is not a problem. The Wayland protocols are designed in a way that client and server can negotiate the version they both support. |