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.OutputStream Finishes an asynchronous stream write operation started with outputStreamWriteAllAsync. As a special exception to the normal conventions for functions that use GError, if this function returns False (and sets error) then bytesWritten will be set to the number of bytes that were successfully written 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 outputStreamWriteAsync. Since: 2.44
-
gi-gio GI.Gio.Objects.OutputStream Tries to write the bytes contained in the nVectors vectors into the stream. Will block during the operation. This function is similar to outputStreamWritev, except it tries to write as many bytes as requested, only stopping on an error. On a successful write of all nVectors vectors, True is returned, and bytesWritten is set to the sum of all the sizes of vectors. 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 bytesWritten will be set to the number of bytes that were successfully written 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 outputStreamWrite. The content of the individual elements of vectors might be changed by this function. Since: 2.60
-
gi-gio GI.Gio.Objects.OutputStream Request an asynchronous write of the bytes contained in the nVectors vectors into the stream. When the operation is finished callback will be called. You can then call outputStreamWritevAllFinish to get the result of the operation. This is the asynchronous version of outputStreamWritevAll. Call outputStreamWritevAllFinish 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. Note that no copy of vectors will be made, so it must stay valid until callback is called. The content of the individual elements of vectors might be changed by this function. Since: 2.60
-
gi-gio GI.Gio.Objects.OutputStream Finishes an asynchronous stream write operation started with outputStreamWritevAllAsync. As a special exception to the normal conventions for functions that use GError, if this function returns False (and sets error) then bytesWritten will be set to the number of bytes that were successfully written 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 outputStreamWritevAsync. Since: 2.60
getPermissionAllowed :: (MonadIO m, IsPermission o) => o -> m Boolgi-gio GI.Gio.Objects.Permission Get the value of the “allowed” property. When overloading is enabled, this is equivalent to
get permission #allowed
permissionGetAllowed :: (HasCallStack, MonadIO m, IsPermission a) => a -> m Boolgi-gio GI.Gio.Objects.Permission Gets the value of the 'allowed' property. This property is True if the caller currently has permission to perform the action that permission represents the permission to perform. Since: 2.26
type
ResolverReloadCallback = IO ()gi-gio GI.Gio.Objects.Resolver Emitted when the resolver notices that the system resolver configuration has changed.
type
SettingsChangeEventCallback = Maybe [Word32] -> IO Boolgi-gio GI.Gio.Objects.Settings The "change-event" signal is emitted once per change event that affects this settings object. You should connect to this signal only if you are interested in viewing groups of changes before they are split out into multiple emissions of the "changed" signal. For most use cases it is more appropriate to use the "changed" signal. In the event that the change event applies to one or more specified keys, keys will be an array of GQuark of length nKeys. In the event that the change event applies to the Settings object as a whole (ie: potentially every key has been changed) then keys will be Nothing and nKeys will be 0. The default handler for this signal invokes the "changed" signal for each affected key. If any other connected handler returns True then this default functionality will be suppressed.
type
SettingsChangedCallback = Text -> IO ()gi-gio GI.Gio.Objects.Settings The "changed" signal is emitted when a key has potentially changed. You should call one of the g_settings_get() calls to check the new value. This signal supports detailed connections. You can connect to the detailed signal "changedx" in order to only receive callbacks when key "x" changes. Note that settings only emits this signal if you have read key at least once while a signal handler was already connected for key.
type
SettingsWritableChangeEventCallback = Word32 -> IO Boolgi-gio GI.Gio.Objects.Settings The "writable-change-event" signal is emitted once per writability change event that affects this settings object. You should connect to this signal if you are interested in viewing groups of changes before they are split out into multiple emissions of the "writable-changed" signal. For most use cases it is more appropriate to use the "writable-changed" signal. In the event that the writability change applies only to a single key, key will be set to the GQuark for that key. In the event that the writability change affects the entire settings object, key will be 0. The default handler for this signal invokes the "writable-changed" and "changed" signals for each affected key. This is done because changes in writability might also imply changes in value (if for example, a new mandatory setting is introduced). If any other connected handler returns True then this default functionality will be suppressed.