Gio.ApplicationFlags

Flags used to define the behaviour of a Gio.Application.

Since 2.28

ApplicationFlags.FLAGS_NONE

Default

ApplicationFlags.IS_SERVICE

Run as a service. In this mode, registration fails if the service is already running, and the application will initially wait up to 10 seconds for an initial activation message to arrive.

ApplicationFlags.IS_LAUNCHER

Don't try to become the primary instance.

ApplicationFlags.HANDLES_OPEN

This application handles opening files (in the primary instance). Note that this flag only affects the default implementation of local_command_line(), and has no effect if Gio.ApplicationFlags.handles_command_line is given. See Gio.Application.prototype.run for details.

ApplicationFlags.HANDLES_COMMAND_LINE

This application handles command line arguments (in the primary instance). Note that this flag only affect the default implementation of local_command_line(). See Gio.Application.prototype.run for details.

ApplicationFlags.SEND_ENVIRONMENT

Send the environment of the launching process to the primary instance. Set this flag if your application is expected to behave differently depending on certain environment variables. For instance, an editor might be expected to use the <envar>GIT_COMMITTER_NAME</envar> environment variable when editing a git commit message. The environment is available to the Gio.Application::command-line signal handler, via Gio.ApplicationCommandLine.prototype.getenv.

ApplicationFlags.NON_UNIQUE

Make no attempts to do any of the typical single-instance application negotiation, even if the application ID is given. The application neither attempts to become the owner of the application ID nor does it check if an existing owner already exists. Everything occurs in the local process. Since: 2.30.