DBusProxyFlags

Added in version 2.26.

class DBusProxyFlags

Flags used when constructing an instance of a DBusProxy derived class.

Fields

class DBusProxyFlags

DO_NOT_AUTO_START

If the proxy is for a well-known name, do not ask the bus to launch an owner during proxy initialization or a method call. This flag is only meaningful in proxies for well-known names.

DO_NOT_AUTO_START_AT_CONSTRUCTION

If the proxy is for a well-known name, do not ask the bus to launch an owner during proxy initialization, but allow it to be autostarted by a method call. This flag is only meaningful in proxies for well-known names, and only if DO_NOT_AUTO_START is not also specified.

DO_NOT_CONNECT_SIGNALS

Don’t connect to signals on the remote object.

DO_NOT_LOAD_PROPERTIES

Don’t load properties.

GET_INVALIDATED_PROPERTIES

If set, the property value for any invalidated property will be (asynchronously) retrieved upon receiving the `PropertiesChanged <http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-properties>`__ D-Bus signal and the property will not cause emission of the DBusProxy::g-properties-changed signal. When the value is received the DBusProxy::g-properties-changed signal is emitted for the property along with the retrieved value. Since 2.32.

NONE

No flags set.

NO_MATCH_RULE

Don’t actually send the AddMatch D-Bus call for this signal subscription. This gives you more control over which match rules you add (but you must add them manually). (Since: 2.72)