ApplicationFlags

Added in version 2.28.

class ApplicationFlags

Flags used to define the behaviour of a Application.

Fields

class ApplicationFlags

ALLOW_REPLACEMENT

Allow another instance to take over the bus name. Since: 2.60

CAN_OVERRIDE_APP_ID

Allow users to override the application ID from the command line with --gapplication-app-id. Since: 2.48

DEFAULT_FLAGS

Default flags. Since: 2.74

FLAGS_NONE

Default. Deprecated in 2.74, use DEFAULT_FLAGS instead

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 run() for details.

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 HANDLES_COMMAND_LINE is given. See run() for details.

IS_LAUNCHER

Don’t try to become the primary instance.

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.

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.

REPLACE

Take over from another instance. This flag is usually set by passing --gapplication-replace on the commandline. Since: 2.60

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 GIT_COMMITTER_NAME environment variable when editing a git commit message. The environment is available to the Application::command-line signal handler, via getenv().