Hoogle Search
Within LTS Haskell 24.52 (ghc-9.10.3)
Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.
-
gi-gio GI.Gio.Objects.DBusAuthObserver Emits the DBusAuthObserver::allowMechanism signal on observer. Since: 2.34
-
gi-gio GI.Gio.Objects.DBusAuthObserver Connect a signal handler for the allowMechanism signal, to be run before the default handler. When overloading is enabled, this is equivalent to
on dBusAuthObserver #allowMechanism callback
type
DBusConnectionClosedCallback = Bool -> Maybe GError -> IO ()gi-gio GI.Gio.Objects.DBusConnection Emitted when the connection is closed. The cause of this event can be
- If dBusConnectionClose is called. In this case remotePeerVanished is set to False and error is Nothing.
- If the remote peer closes the connection. In this case remotePeerVanished is set to True and error is set.
- If the remote peer sends invalid or malformed data. In this case remotePeerVanished is set to False and error is set.
-
gi-gio GI.Gio.Objects.DBusConnection Asynchronously invokes the methodName method on the interfaceName D-Bus interface on the remote object at objectPath owned by busName. If connection is closed then the operation will fail with IOErrorEnumClosed. If cancellable is canceled, the operation will fail with IOErrorEnumCancelled. If parameters contains a value not compatible with the D-Bus protocol, the operation fails with IOErrorEnumInvalidArgument. If replyType is non-Nothing then the reply will be checked for having this type and an error will be raised if it does not match. Said another way, if you give a replyType then any non-Nothing return value will be of this type. Unless it’s G_VARIANT_TYPE_UNIT, the replyType will be a tuple containing one or more values. If the parameters GVariant is floating, it is consumed. This allows convenient 'inline' use of g_variant_new(), e.g.:
C code
g_dbus_connection_call (connection, "org.freedesktop.StringThings", "/org/freedesktop/StringThings", "org.freedesktop.StringThings", "TwoStrings", g_variant_new ("(ss)", "Thing One", "Thing Two"), NULL, G_DBUS_CALL_FLAGS_NONE, -1, NULL, (GAsyncReadyCallback) two_strings_done, NULL);This is an asynchronous method. When the operation is finished, callback will be invoked in the [thread-default main context][g-main-context-push-thread-default] of the thread you are calling this method from. You can then call dBusConnectionCallFinish to get the result of the operation. See dBusConnectionCallSync for the synchronous version of this function. If callback is Nothing then the D-Bus method call message will be sent with the DBusMessageFlagsNoReplyExpected flag set. Since: 2.26 -
gi-gio GI.Gio.Objects.DBusConnection Finishes an operation started with dBusConnectionCall. Since: 2.26
-
gi-gio GI.Gio.Objects.DBusConnection Synchronously invokes the methodName method on the interfaceName D-Bus interface on the remote object at objectPath owned by busName. If connection is closed then the operation will fail with IOErrorEnumClosed. If cancellable is canceled, the operation will fail with IOErrorEnumCancelled. If parameters contains a value not compatible with the D-Bus protocol, the operation fails with IOErrorEnumInvalidArgument. If replyType is non-Nothing then the reply will be checked for having this type and an error will be raised if it does not match. Said another way, if you give a replyType then any non-Nothing return value will be of this type. If the parameters GVariant is floating, it is consumed. This allows convenient 'inline' use of g_variant_new(), e.g.:
C code
g_dbus_connection_call_sync (connection, "org.freedesktop.StringThings", "/org/freedesktop/StringThings", "org.freedesktop.StringThings", "TwoStrings", g_variant_new ("(ss)", "Thing One", "Thing Two"), NULL, G_DBUS_CALL_FLAGS_NONE, -1, NULL, &error);The calling thread is blocked until a reply is received. See dBusConnectionCall for the asynchronous version of this method. Since: 2.26 -
gi-gio GI.Gio.Objects.DBusConnection Like dBusConnectionCall but also takes a UnixFDList object. The file descriptors normally correspond to G_VARIANT_TYPE_HANDLE values in the body of the message. For example, if a message contains two file descriptors, fdList would have length 2, and g_variant_new_handle (0) and g_variant_new_handle (1) would appear somewhere in the body of the message (not necessarily in that order!) to represent the file descriptors at indexes 0 and 1 respectively. When designing D-Bus APIs that are intended to be interoperable, please note that non-GDBus implementations of D-Bus can usually only access file descriptors if they are referenced in this way by a value of type G_VARIANT_TYPE_HANDLE in the body of the message. This method is only available on UNIX. Since: 2.30
-
gi-gio GI.Gio.Objects.DBusConnection Finishes an operation started with dBusConnectionCallWithUnixFdList. The file descriptors normally correspond to G_VARIANT_TYPE_HANDLE values in the body of the message. For example, if variantGetHandle returns 5, that is intended to be a reference to the file descriptor that can be accessed by g_unix_fd_list_get (*out_fd_list, 5, ...). When designing D-Bus APIs that are intended to be interoperable, please note that non-GDBus implementations of D-Bus can usually only access file descriptors if they are referenced in this way by a value of type G_VARIANT_TYPE_HANDLE in the body of the message. Since: 2.30
-
gi-gio GI.Gio.Objects.DBusConnection Like dBusConnectionCallSync but also takes and returns UnixFDList objects. See dBusConnectionCallWithUnixFdList and dBusConnectionCallWithUnixFdListFinish for more details. This method is only available on UNIX. Since: 2.30
type
DBusInterfaceSkeletonGAuthorizeMethodCallback = DBusMethodInvocation -> IO Boolgi-gio GI.Gio.Objects.DBusInterfaceSkeleton Emitted when a method is invoked by a remote caller and used to determine if the method call is authorized. Note that this signal is emitted in a thread dedicated to handling the method call so handlers are allowed to perform blocking IO. This means that it is appropriate to call e.g. polkit_authority_check_authorization_sync() with the POLKIT_CHECK_AUTHORIZATION_FLAGS_ALLOW_USER_INTERACTION flag set. If False is returned then no further handlers are run and the signal handler must take a reference to invocation and finish handling the call (e.g. return an error via g_dbus_method_invocation_return_error()). Otherwise, if True is returned, signal emission continues. If no handlers return False, then the method is dispatched. If interface has an enclosing DBusObjectSkeleton, then the DBusObjectSkeleton::authorizeMethod signal handlers run before the handlers for this signal. The default class handler just returns True. Please note that the common case is optimized: if no signals handlers are connected and the default class handler isn't overridden (for both interface and the enclosing DBusObjectSkeleton, if any) and DBusInterfaceSkeleton:gFlags does not have the DBusInterfaceSkeletonFlagsHandleMethodInvocationsInThread flags set, no dedicated thread is ever used and the call will be handled in the same thread as the object that interface belongs to was exported in. Since: 2.30