From 7bd037fae43c963d5f67e9447b3ee6875591a2c7 Mon Sep 17 00:00:00 2001 From: Christian Mollekopf Date: Thu, 15 Dec 2016 17:26:59 +0100 Subject: Don't set capabilities as property on creation. Instead we make it part of the plugin. This ensure we also have access to the proper capabilities when creating a resource via sinksh. --- examples/dummyresource/resourcefactory.cpp | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'examples/dummyresource') diff --git a/examples/dummyresource/resourcefactory.cpp b/examples/dummyresource/resourcefactory.cpp index 03238ef..0663bdb 100644 --- a/examples/dummyresource/resourcefactory.cpp +++ b/examples/dummyresource/resourcefactory.cpp @@ -176,7 +176,7 @@ DummyResource::~DummyResource() } DummyResourceFactory::DummyResourceFactory(QObject *parent) - : Sink::ResourceFactory(parent) + : Sink::ResourceFactory(parent, QByteArrayList() << Sink::ApplicationDomain::ResourceCapabilities::Mail::storage << "-folder.rename" << Sink::ApplicationDomain::ResourceCapabilities::Mail::sent) { } @@ -204,3 +204,4 @@ void DummyResourceFactory::removeDataFromDisk(const QByteArray &instanceIdentifi { DummyResource::removeFromDisk(instanceIdentifier); } + -- cgit v1.2.3