Properly handle destroying a Pointer resource

Authored by graesslin on Jun 28 2016, 4:57 PM.

Description

Properly handle destroying a Pointer resource

Summary:
On client side the newer wl_pointer_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
PointerInterface between unbound and destroyed.

Test Plan:
Test case extended to cover the condition of an unbound
PointerInterface.

Reviewers: Plasma on Wayland

Subscribers: plasma-devel

Tags: Plasma on Wayland

Differential Revision: https://phabricator.kde.org/D2037

Details

Committed
graesslinJun 28 2016, 4:58 PM
Differential Revision
D2037: Properly handle destroying a Pointer resource
Parents
R127:8dce022ced24: [autotests] Get Server::Cursor::pointer under coverage
Branches
Unknown
Tags
Unknown