From 962ff7b523d81249dfc1eb6870b7a6249893e2ea Mon Sep 17 00:00:00 2001 From: David Wagner Date: Fri, 16 Jan 2015 16:59:06 +0100 Subject: ParameterMgr: add a method to forcefully disable the remote interface In some setup, users might not want to start the remote interface even if the toplevel configuration file allows it. The parameter-framework client can now override the remote interface starting policy. This was, until now, only dictated by the 'TuningAllowed' attribute in the toplevel configuration file and the presence of the libremote-processor library. This method is forwarded to the connectors and the bindings. Change-Id: Ib6dc272dfc7114125fdafd1a58642cde88847752 Signed-off-by: David Wagner --- bindings/python/pfw.i | 3 +++ 1 file changed, 3 insertions(+) (limited to 'bindings') diff --git a/bindings/python/pfw.i b/bindings/python/pfw.i index da01cdc..ce27173 100644 --- a/bindings/python/pfw.i +++ b/bindings/python/pfw.i @@ -88,6 +88,9 @@ public: // Configuration application void applyConfigurations(); + bool getForceNoRemoteInterface() const; + void setForceNoRemoteInterface(bool bForceNoRemoteInterface); + void setFailureOnMissingSubsystem(bool bFail); bool getFailureOnMissingSubsystem() const; -- cgit v1.1