[server] Do not own dmabuf implementation

Summary:
The dmabuf implementation should be managed by the compositor and not by the
interface which might go away through signals while the implementation goes
away in the compositor simultaneously.

Test Plan: Compiles.

Reviewers: #kwin, davidedmundson

Reviewed By: #kwin, davidedmundson

Subscribers: kde-frameworks-devel

Tags: #frameworks

Differential Revision: https://phabricator.kde.org/D25576
This commit is contained in:
Roman Gilg 2019-11-27 20:39:48 +01:00
parent 443721b555
commit 663d780e71
2 changed files with 3 additions and 4 deletions

View file

@ -428,10 +428,7 @@ V1Iface::Private::Private(V1Iface *q, Display *display)
{ {
} }
V1Iface::Private::~Private() V1Iface::Private::~Private() = default;
{
delete impl;
}
void V1Iface::Private::bind(wl_client *client, uint32_t version, uint32_t id) void V1Iface::Private::bind(wl_client *client, uint32_t version, uint32_t id)
{ {

View file

@ -146,6 +146,8 @@ public:
/** /**
* Sets the compositor implementation for the dmabuf interface. * Sets the compositor implementation for the dmabuf interface.
*
* The ownership is not transferred by this call.
*/ */
void setImpl(Impl *impl); void setImpl(Impl *impl);