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/mailtransportresource/mailtransportresource.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'examples/mailtransportresource') diff --git a/examples/mailtransportresource/mailtransportresource.cpp b/examples/mailtransportresource/mailtransportresource.cpp index b7ee77a..cf657f3 100644 --- a/examples/mailtransportresource/mailtransportresource.cpp +++ b/examples/mailtransportresource/mailtransportresource.cpp @@ -186,7 +186,7 @@ MailtransportResource::MailtransportResource(const Sink::ResourceContext &resour } MailtransportResourceFactory::MailtransportResourceFactory(QObject *parent) - : Sink::ResourceFactory(parent) + : Sink::ResourceFactory(parent, {Sink::ApplicationDomain::ResourceCapabilities::Mail::transport}) { } -- cgit v1.2.3