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.

  1. type DtlsConnectionAcceptCertificateCallback = TlsCertificate -> [TlsCertificateFlags] -> IO Bool

    gi-gio GI.Gio.Interfaces.DtlsConnection

    Emitted during the TLS handshake after the peer certificate has been received. You can examine peerCert's certification path by calling tlsCertificateGetIssuer on it. For a client-side connection, peerCert is the server's certificate, and the signal will only be emitted if the certificate was not acceptable according to conn's DtlsClientConnection:validation_flags. If you would like the certificate to be accepted despite errors, return True from the signal handler. Otherwise, if no handler accepts the certificate, the handshake will fail with TlsErrorBadCertificate. GLib guarantees that if certificate verification fails, this signal will be emitted with at least one error will be set in errors, but it does not guarantee that all possible errors will be set. Accordingly, you may not safely decide to ignore any particular type of error. For example, it would be incorrect to ignore TlsCertificateFlagsExpired if you want to allow expired certificates, because this could potentially be the only error flag set even if other problems exist with the certificate. For a server-side connection, peerCert is the certificate presented by the client, if this was requested via the server's DtlsServerConnection:authentication_mode. On the server side, the signal is always emitted when the client presents a certificate, and the certificate will only be accepted if a handler returns True. Note that if this signal is emitted as part of asynchronous I/O in the main thread, then you should not attempt to interact with the user before returning from the signal handler. If you want to let the user decide whether or not to accept the certificate, you would have to return False from the signal handler on the first attempt, and then after the connection attempt returns a TlsErrorBadCertificate, you can interact with the user, and if the user decides to accept the certificate, remember that fact, create a new connection, and return True from the signal handler the next time. If you are doing I/O in another thread, you do not need to worry about this, and can simply block in the signal handler until the UI thread returns an answer. Since: 2.48

  2. type ListModelItemsChangedCallback = Word32 -> Word32 -> Word32 -> IO ()

    gi-gio GI.Gio.Interfaces.ListModel

    This signal is emitted whenever items were added to or removed from list. At position, removed items were removed and added items were added in their place. Note: If removed != added, the positions of all later items in the model change. Since: 2.44

  3. type MemoryMonitorLowMemoryWarningCallback = MemoryMonitorWarningLevel -> IO ()

    gi-gio GI.Gio.Interfaces.MemoryMonitor

    Emitted when the system is running low on free memory. The signal handler should then take the appropriate action depending on the warning level. See the MemoryMonitorWarningLevel documentation for details. Since: 2.64

  4. type MountChangedCallback = IO ()

    gi-gio GI.Gio.Interfaces.Mount

    Emitted when the mount has been changed.

  5. type MountPreUnmountCallback = IO ()

    gi-gio GI.Gio.Interfaces.Mount

    This signal may be emitted when the Mount is about to be unmounted. This signal depends on the backend and is only emitted if GIO was used to unmount. Since: 2.22

  6. type MountUnmountedCallback = IO ()

    gi-gio GI.Gio.Interfaces.Mount

    This signal is emitted when the Mount have been unmounted. If the recipient is holding references to the object they should release them so the object can be finalized.

  7. type NetworkMonitorNetworkChangedCallback = Bool -> IO ()

    gi-gio GI.Gio.Interfaces.NetworkMonitor

    Emitted when the network configuration changes. Since: 2.32

  8. type VolumeChangedCallback = IO ()

    gi-gio GI.Gio.Interfaces.Volume

    Emitted when the volume has been changed.

  9. type VolumeRemovedCallback = IO ()

    gi-gio GI.Gio.Interfaces.Volume

    This signal is emitted when the Volume have been removed. If the recipient is holding references to the object they should release them so the object can be finalized.

  10. type AppInfoMonitorChangedCallback = IO ()

    gi-gio GI.Gio.Objects.AppInfoMonitor

    Signal emitted when the app info database changes, when applications are installed or removed. Since: 2.40

Page 453 of many | Previous | Next