glib-0.13.10.0: Binding to the GLIB library for Gtk2Hs.

Maintainer | gtk2hs-users@lists.sourceforge.net
Stability | provisional
Portability | portable (depends on GHC)
Safe Haskell | Safe-Inferred
Language | Haskell98

System.Glib.Utils

Description

This module binds GLib-specific utility procedures.

Synopsis

- getApplicationName :: GlibString string => IO (Maybe string)
- setApplicationName :: GlibString string => string -> IO ()
- getProgramName :: GlibString string => IO (Maybe string)
- setProgramName :: GlibString string => string -> IO ()

# Documentation

getApplicationName :: GlibString string => IO (Maybe string) Source #

Gets a human-readable name for the application, as set by `setApplicationName`. This name should be localized if possible, and is intended for display to the user. Contrast with `getProgramName`, which gets a non-localized name. If `setApplicationName` has not been performed, returns the result of `getProgramName` (which may be `Nothing` if `setProgramName` has also not been performed).

setApplicationName :: GlibString string => string -> IO () Source #

Sets a human-readable name for the application. This name should be localized if possible, and is intended for display to the user. Contrast with `setProgramName`, which sets a non-localized name. `setProgramName` will be performed automatically by `initGUI`, but `setApplicationName` will not.

Note that for thread safety reasons, this computation can only be performed once.

The application name will be used in contexts such as error messages, or when displaying an application's name in the task list.

getProgramName :: GlibString string => IO (Maybe string) Source #

Gets the name of the program. This name should not be localized, contrast with `getApplicationName`. If you are using GDK or GTK+, the program name is set in `initGUI` to the last component of argv[0].

setProgramName :: GlibString string => string -> IO () Source #

Sets the name of the program. This name should not be localized, contrast with `setApplicationName`. Note that for thread-safety reasons this computation can only be performed once.