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.
type
AppLaunchContextLaunchFailedCallback = Text -> IO ()gi-gio GI.Gio.Objects.AppLaunchContext The AppLaunchContext::launchFailed signal is emitted when a AppInfo launch fails. The startup notification id is provided, so that the launcher can cancel the startup notification. Because a launch operation may involve spawning multiple instances of the target application, you should expect this signal to be emitted multiple times, one for each spawned instance. Since: 2.36
type
AppLaunchContextLaunchStartedCallback = AppInfo -> Maybe GVariant -> IO ()gi-gio GI.Gio.Objects.AppLaunchContext The AppLaunchContext::launchStarted signal is emitted when a AppInfo is about to be launched. If non-null the platformData is an GVariant dictionary mapping strings to variants (ie a{sv}), which contains additional, platform-specific data about this launch. On UNIX, at least the startup-notification-id keys will be present. The value of the startup-notification-id key (type s) is a startup notification ID corresponding to the format from the <https://specifications.freedesktop.org/startup-notification-spec/startup-notification-0.1.txt startup-notification specification>. It allows tracking the progress of the launchee through startup. It is guaranteed that this signal is followed by either a AppLaunchContext::launched or AppLaunchContext::launchFailed signal. Because a launch operation may involve spawning multiple instances of the target application, you should expect this signal to be emitted multiple times, one for each spawned instance. Since: 2.72
type
AppLaunchContextLaunchedCallback = AppInfo -> GVariant -> IO ()gi-gio GI.Gio.Objects.AppLaunchContext The AppLaunchContext::launched signal is emitted when a AppInfo is successfully launched. Because a launch operation may involve spawning multiple instances of the target application, you should expect this signal to be emitted multiple times, one time for each spawned instance. The platformData is an GVariant dictionary mapping strings to variants (ie a{sv}), which contains additional, platform-specific data about this launch. On UNIX, at least the pid and startup-notification-id keys will be present. Since 2.72 the pid may be 0 if the process id wasn't known (for example if the process was launched via D-Bus). The pid may not be set at all in subsequent releases. On Windows, pid is guaranteed to be valid only for the duration of the AppLaunchContext::launched signal emission; after the signal is emitted, GLib will call spawnClosePid. If you need to keep the GPid after the signal has been emitted, then you can duplicate pid using DuplicateHandle(). Since: 2.36
type
ApplicationActivateCallback = IO ()gi-gio GI.Gio.Objects.Application The activate signal is emitted on the primary instance when an activation occurs. See applicationActivate.
type
ApplicationCommandLineCallback = ApplicationCommandLine -> IO Int32gi-gio GI.Gio.Objects.Application The commandLine signal is emitted on the primary instance when a commandline is not handled locally. See applicationRun and the ApplicationCommandLine documentation for more information.
type
ApplicationHandleLocalOptionsCallback = VariantDict -> IO Int32gi-gio GI.Gio.Objects.Application The handleLocalOptions signal is emitted on the local instance after the parsing of the commandline options has occurred. You can add options to be recognised during commandline option parsing using applicationAddMainOptionEntries and applicationAddOptionGroup. Signal handlers can inspect options (along with values pointed to from the argData of an installed GOptionEntrys) in order to decide to perform certain actions, including direct local handling (which may be useful for options like --version). In the event that the application is marked ApplicationFlagsHandlesCommandLine the "normal processing" will send the options dictionary to the primary instance where it can be read with applicationCommandLineGetOptionsDict. The signal handler can modify the dictionary before returning, and the modified dictionary will be sent. In the event that ApplicationFlagsHandlesCommandLine is not set, "normal processing" will treat the remaining uncollected command line arguments as filenames or URIs. If there are no arguments, the application is activated by applicationActivate. One or more arguments results in a call to applicationOpen. If you want to handle the local commandline arguments for yourself by converting them to calls to applicationOpen or actionGroupActivateAction then you must be sure to register the application first. You should probably not call applicationActivate for yourself, however: just return -1 and allow the default handler to do it for you. This will ensure that the --gapplication-service switch works properly (i.e. no activation in that case). Note that this signal is emitted from the default implementation of local_command_line(). If you override that function and don't chain up then this signal will never be emitted. You can override local_command_line() if you need more powerful capabilities than what is provided here, but this should not normally be required. Since: 2.40
type
ApplicationNameLostCallback = IO Boolgi-gio GI.Gio.Objects.Application The nameLost signal is emitted only on the registered primary instance when a new instance has taken over. This can only happen if the application is using the ApplicationFlagsAllowReplacement flag. The default handler for this signal calls applicationQuit. Since: 2.60
type
ApplicationOpenCallback = [File] -> Text -> IO ()gi-gio GI.Gio.Objects.Application The open signal is emitted on the primary instance when there are files to open. See applicationOpen for more information.
type
ApplicationShutdownCallback = IO ()gi-gio GI.Gio.Objects.Application The shutdown signal is emitted only on the registered primary instance immediately after the main loop terminates.
type
ApplicationStartupCallback = IO ()gi-gio GI.Gio.Objects.Application The startup signal is emitted on the primary instance immediately after registration. See applicationRegister.