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.DBusProxy Finishes an operation started with dBusProxyCallWithUnixFdList. Since: 2.30
-
gi-gio GI.Gio.Objects.DBusProxy Like dBusProxyCallSync but also takes and returns UnixFDList objects. This method is only available on UNIX. Since: 2.30
type
DBusServerNewConnectionCallback = DBusConnection -> IO Boolgi-gio GI.Gio.Objects.DBusServer Emitted when a new authenticated connection has been made. Use dBusConnectionGetPeerCredentials to figure out what identity (if any), was authenticated. If you want to accept the connection, take a reference to the connection object and return True. When you are done with the connection call dBusConnectionClose and give up your reference. Note that the other peer may disconnect at any time - a typical thing to do when accepting a connection is to listen to the DBusConnection::closed signal. If DBusServer:flags contains DBusServerFlagsRunInThread then the signal is emitted in a new thread dedicated to the connection. Otherwise the signal is emitted in the [thread-default main context][g-main-context-push-thread-default] of the thread that server was constructed in. You are guaranteed that signal handlers for this signal runs before incoming messages on connection are processed. This means that it's suitable to call g_dbus_connection_register_object() or similar from the signal handler. Since: 2.26
type
DebugControllerDBusAuthorizeCallback = DBusMethodInvocation -> IO Boolgi-gio GI.Gio.Objects.DebugControllerDBus Emitted when a D-Bus peer is trying to change the debug settings and used to determine if that is authorized. This signal is emitted in a dedicated worker thread, so handlers are allowed to perform blocking I/O. This means that, for example, it is appropriate to call polkit_authority_check_authorization_sync() to check authorization using polkit. If False is returned then no further handlers are run and the request to change the debug settings is rejected. Otherwise, if True is returned, signal emission continues. If no handlers return False, then the debug settings are allowed to be changed. Signal handlers must not modify invocation, or cause it to return a value. The default class handler just returns True. Since: 2.72
type
FileMonitorChangedCallback = File -> Maybe File -> FileMonitorEvent -> IO ()gi-gio GI.Gio.Objects.FileMonitor Emitted when file has been changed. If using FileMonitorFlagsWatchMoves on a directory monitor, and the information is available (and if supported by the backend), eventType may be FileMonitorEventRenamed, FileMonitorEventMovedIn or FileMonitorEventMovedOut. In all cases file will be a child of the monitored directory. For renames, file will be the old name and otherFile is the new name. For "moved in" events, file is the name of the file that appeared and otherFile is the old name that it was moved from (in another directory). For "moved out" events, file is the name of the file that used to be in this directory and otherFile is the name of the file at its new location. It makes sense to treat FileMonitorEventMovedIn as equivalent to FileMonitorEventCreated and FileMonitorEventMovedOut as equivalent to FileMonitorEventDeleted, with extra information. FileMonitorEventRenamed is equivalent to a delete/create pair. This is exactly how the events will be reported in the case that the FileMonitorFlagsWatchMoves flag is not in use. If using the deprecated flag FileMonitorFlagsSendMoved flag and eventType is FileMonitorEventMoved, file will be set to a File containing the old path, and otherFile will be set to a File containing the new path. In all the other cases, otherFile will be set to NULL.
type
FilenameCompleterGotCompletionDataCallback = IO ()gi-gio GI.Gio.Objects.FilenameCompleter Emitted when the file name completion information comes available.
-
gi-gio GI.Gio.Objects.InputStream Tries to read count bytes from the stream into the buffer starting at buffer. Will block during this read. This function is similar to inputStreamRead, except it tries to read as many bytes as requested, only stopping on an error or end of stream. On a successful read of count bytes, or if we reached the end of the stream, True is returned, and bytesRead is set to the number of bytes read into buffer. If there is an error during the operation False is returned and error is set to indicate the error status. As a special exception to the normal conventions for functions that use GError, if this function returns False (and sets error) then bytesRead will be set to the number of bytes that were successfully read before the error was encountered. This functionality is only available from C. If you need it from another language then you must write your own loop around inputStreamRead.
-
gi-gio GI.Gio.Objects.InputStream Request an asynchronous read of count bytes from the stream into the buffer starting at buffer. This is the asynchronous equivalent of inputStreamReadAll. Call inputStreamReadAllFinish to collect the result. Any outstanding I/O request with higher priority (lower numerical value) will be executed before an outstanding request with lower priority. Default priority is PRIORITY_DEFAULT. Since: 2.44
-
gi-gio GI.Gio.Objects.InputStream Finishes an asynchronous stream read operation started with inputStreamReadAllAsync. As a special exception to the normal conventions for functions that use GError, if this function returns False (and sets error) then bytesRead will be set to the number of bytes that were successfully read before the error was encountered. This functionality is only available from C. If you need it from another language then you must write your own loop around inputStreamReadAsync. Since: 2.44
listStoreRemoveAll :: (HasCallStack, MonadIO m, IsListStore a) => a -> m ()gi-gio GI.Gio.Objects.ListStore Removes all items from store. Since: 2.44