Creates a new #GSettings object with the schema specified by schema_id.
Applies any changes that have been made to the settings. This function does nothing unless settings is in 'delay-apply' mode; see gio.settings.Settings.delay. In the normal case settings are always applied immediately.
Create a binding between the key in the settings object and the property property of object.
Create a binding between the writability of key in the settings object and the property property of object. The property must be boolean; "sensitive" or "visible" properties of widgets are the most likely candidates.
Connect to ChangeEvent signal.
Connect to Changed signal.
Connect to WritableChangeEvent signal.
Connect to WritableChanged signal.
Creates a #GAction corresponding to a given #GSettings key.
Changes the #GSettings object into 'delay-apply' mode. In this mode, changes to settings are not immediately propagated to the backend, but kept locally until gio.settings.Settings.apply is called.
Gets the value that is stored at key in settings.
Creates a child settings object which has a base path of base-path/name, where base-path is the base path of settings.
Gets the "default value" of a key.
Gets the value that is stored at key in settings.
Gets the value that is stored in settings for key and converts it to the enum value that it represents.
Gets the value that is stored in settings for key and converts it to the flags value that it represents.
Returns whether the #GSettings object has any unapplied changes. This can only be the case if it is in 'delayed-apply' mode.
Gets the value that is stored at key in settings.
Gets the value that is stored at key in settings.
Gets the value that is stored at key in settings, subject to application-level validation/mapping.
Queries the range of a key.
Gets the value that is stored at key in settings.
A convenience variant of gio.settings.Settings.get for string arrays.
Gets the value that is stored at key in settings.
Gets the value that is stored at key in settings.
Checks the "user value" of a key, if there is one.
Gets the value that is stored in settings for key.
Finds out if a key can be written or not
Gets the list of children on settings.
Introspects the list of keys on settings.
Checks if the given value is of the correct type and within the permitted range for key.
Resets key to its default value.
Reverts all non-applied changes to the settings. This function does nothing unless settings is in 'delay-apply' mode; see gio.settings.Settings.delay. In the normal case settings are always applied immediately.
Sets key in settings to value.
Sets key in settings to value.
Looks up the enumerated type nick for value and writes it to key, within settings.
Looks up the flags type nicks for the bits specified by value, puts them in an array of strings and writes the array to key, within settings.
Sets key in settings to value.
Sets key in settings to value.
Sets key in settings to value.
Sets key in settings to value.
Sets key in settings to value.
Sets key in settings to value.
Sets key in settings to value.
Deprecated.
Deprecated.
Creates a new #GSettings object with a given schema, backend and path.
Creates a new #GSettings object with the schema specified by schema_id and a given #GSettingsBackend.
Creates a new #GSettings object with the schema specified by schema_id and a given #GSettingsBackend and path.
Creates a new #GSettings object with the relocatable schema specified by schema_id and a given path.
Ensures that all pending operations are complete for the default backend.
Removes an existing binding for property on object.
Set the GObject of a D ObjectG wrapper.
Get a pointer to the underlying C object.
Calls g_object_ref() on a GObject.
Calls g_object_unref() on a GObject.
Get the GType of an object.
GObject GType property.
Convenience method to return this cast to a type. For use in D with statements.
Template to get the D object from a C GObject and cast it to the given D object type.
Connect a D closure to an object signal.
Template for setting a GObject property.
Template for getting a GObject property.
Creates a binding between source_property on source and target_property on target.
Creates a binding between source_property on source and target_property on target, allowing you to set the transformation functions to be used by the binding.
This function is intended for #GObject implementations to re-enforce a floating[floating-ref] object reference. Doing this is seldom required: all #GInitiallyUnowneds are created with a floating reference which usually just needs to be sunken by calling gobject.object.ObjectG.refSink.
Increases the freeze count on object. If the freeze count is non-zero, the emission of "notify" signals on object is stopped. The signals are queued until the freeze count is decreased to zero. Duplicate notifications are squashed so that at most one #GObject::notify signal is emitted for each property modified while the object is frozen.
Gets a named field from the objects table of associations (see gobject.object.ObjectG.setData).
Gets a property of an object.
This function gets back user data pointers stored via gobject.object.ObjectG.setQdata.
Gets n_properties properties for an object. Obtained properties will be set to values. All properties must be valid. Warnings will be emitted and undefined behaviour may result if invalid properties are passed in.
Checks whether object has a floating[floating-ref] reference.
Emits a "notify" signal for the property property_name on object.
Emits a "notify" signal for the property specified by pspec on object.
Increase the reference count of object, and possibly remove the floating[floating-ref] reference, if object has a floating reference.
Releases all references to other objects. This can be used to break reference cycles.
Each object carries around a table of associations from strings to pointers. This function lets you set an association.
Sets a property on an object.
Remove a specified datum from the object's data associations, without invoking the association's destroy handler.
This function gets back user data pointers stored via gobject.object.ObjectG.setQdata and removes the data from object without invoking its destroy() function (if any was set). Usually, calling this function is only required to update user data pointers with a destroy notifier, for example:
Reverts the effect of a previous call to gobject.object.ObjectG.freezeNotify. The freeze count is decreased on object and when it reaches zero, queued "notify" signals are emitted.
This function essentially limits the life time of the closure to the life time of the object. That is, when the object is finalized, the closure is invalidated by calling gobject.closure.Closure.invalidate on it, in order to prevent invocations of the closure with a finalized (nonexisting) object. Also, gobject.object.ObjectG.ref_ and gobject.object.ObjectG.unref are added as marshal guards to the closure, to ensure that an extra reference count is held on object during invocation of the closure. Usually, this function will be called on closures that use this object as closure data.
Connect to Notify signal.
The gio.settings.Settings class provides a convenient API for storing and retrieving application settings.
Reads and writes can be considered to be non-blocking. Reading settings with gio.settings.Settings is typically extremely fast: on approximately the same order of magnitude (but slower than) a glib.hash_table.HashTable lookup. Writing settings is also extremely fast in terms of time to return to your application, but can be extremely expensive for other threads and other processes. Many settings backends (including dconf) have lazy initialisation which means in the common case of the user using their computer without modifying any settings a lot of work can be avoided. For dconf, the D-Bus service doesn’t even need to be started in this case. For this reason, you should only ever modify gio.settings.Settings keys in response to explicit user action. Particular care should be paid to ensure that modifications are not made during startup — for example, when setting the initial value of preferences widgets. The built-in gio.settings.Settings.bind functionality is careful not to write settings in response to notify signals as a result of modifications that it makes to widgets.
When creating a gio.settings.Settings instance, you have to specify a schema that describes the keys in your settings and their types and default values, as well as some other information.
Normally, a schema has a fixed path that determines where the settings are stored in the conceptual global tree of settings. However, schemas can also be ‘relocatable’, i.e. not equipped with a fixed path. This is useful e.g. when the schema describes an ‘account’, and you want to be able to store a arbitrary number of accounts.
Paths must start with and end with a forward slash character (/) and must not contain two sequential slash characters. Paths should be chosen based on a domain name associated with the program or library to which the settings belong. Examples of paths are /org/gtk/settings/file-chooser/ and /ca/desrt/dconf-editor/. Paths should not start with /apps/, /desktop/ or /system/ as they often did in GConf.
Unlike other configuration systems (like GConf), GSettings does not restrict keys to basic types like strings and numbers. GSettings stores values as glib.variant.VariantG, and allows any glib.variant_type.VariantType for keys. Key names are restricted to lowercase characters, numbers and -. Furthermore, the names must begin with a lowercase character, must not end with a -, and must not contain consecutive dashes.
Similar to GConf, the default values in GSettings schemas can be localized, but the localized values are stored in gettext catalogs and looked up with the domain that is specified in the gettext-domain attribute of the <schemalist> or <schema> elements and the category that is specified in the l10n attribute of the <default> element. The string which is translated includes all text in the <default> element, including any surrounding quotation marks.
The l10n attribute must be set to messages or time, and sets the [locale category for translation](https://www.gnu.org/software/gettext/manual/html_node/Aspects.html#index-locale-categories-1). The messages category should be used by default; use time for translatable date or time formats. A translation comment can be added as an XML comment immediately above the <default> element — it is recommended to add these comments to aid translators understand the meaning and implications of the default value. An optional translation context attribute can be set on the <default> element to disambiguate multiple defaults which use the same string.
For example:
Translations of default values must remain syntactically valid serialized glib.variant.VariantGs (e.g. retaining any surrounding quotation marks) or runtime errors will occur.
GSettings uses schemas in a compact binary form that is created by the `glib-compile-schemas` utility. The input is a schema description in an XML format.
A DTD for the gschema XML format can be found here: gschema.dtd
The `glib-compile-schemas` tool expects schema files to have the extension .gschema.xml.
At runtime, schemas are identified by their ID (as specified in the id attribute of the <schema> element). The convention for schema IDs is to use a dotted name, similar in style to a D-Bus bus name, e.g. org.gnome.SessionManager. In particular, if the settings are for a specific service that owns a D-Bus bus name, the D-Bus bus name and schema ID should match. For schemas which deal with settings not associated with one named application, the ID should not use StudlyCaps, e.g. org.gnome.font-rendering.
In addition to glib.variant.VariantG types, keys can have types that have enumerated types. These can be described by a <choice>, <enum> or <flags> element, as seen in the second example below. The underlying type of such a key is string, but you can use gio.settings.Settings.getEnum, gio.settings.Settings.setEnum, gio.settings.Settings.getFlags, gio.settings.Settings.setFlags access the numeric values corresponding to the string value of enum and flags keys.
An example for default value:
An example for ranges, choices and enumerated types:
Vendor overrides
Default values are defined in the schemas that get installed by an application. Sometimes, it is necessary for a vendor or distributor to adjust these defaults. Since patching the XML source for the schema is inconvenient and error-prone, `glib-compile-schemas` reads so-called ‘vendor override’ files. These are keyfiles in the same directory as the XML schema sources which can override default values. The schema ID serves as the group name in the key file, and the values are expected in serialized glib.variant.VariantG form, as in the following example:
glib-compile-schemas expects schema files to have the extension .gschema.override.
Binding
A very convenient feature of GSettings lets you bind gobject.object.ObjectG properties directly to settings, using gio.settings.Settings.bind. Once a gobject.object.ObjectG property has been bound to a setting, changes on either side are automatically propagated to the other side. GSettings handles details like mapping between gobject.object.ObjectG and glib.variant.VariantG types, and preventing infinite cycles.
This makes it very easy to hook up a preferences dialog to the underlying settings. To make this even more convenient, GSettings looks for a boolean property with the name sensitivity and automatically binds it to the writability of the bound setting. If this ‘magic’ gets in the way, it can be suppressed with the gio.types.SettingsBindFlags.NoSensitivity flag.
Relocatable schemas
A relocatable schema is one with no path attribute specified on its <schema> element. By using gio.settings.Settings.newWithPath, a gio.settings.Settings object can be instantiated for a relocatable schema, assigning a path to the instance. Paths passed to gio.settings.Settings.newWithPath will typically be constructed dynamically from a constant prefix plus some form of instance identifier; but they must still be valid GSettings paths. Paths could also be constant and used with a globally installed schema originating from a dependency library.
For example, a relocatable schema could be used to store geometry information for different windows in an application. If the schema ID was org.foo.MyApp.Window, it could be instantiated for paths /org/foo/MyApp/main/, /org/foo/MyApp/document-1/, /org/foo/MyApp/document-2/, etc. If any of the paths are well-known they can be specified as <child> elements in the parent schema, e.g.:
Build system integration
GSettings comes with autotools integration to simplify compiling and installing schemas. To add GSettings support to an application, add the following to your configure.ac:
In the appropriate Makefile.am, use the following snippet to compile and install the named schema:
No changes are needed to the build system to mark a schema XML file for translation. Assuming it sets the gettext-domain attribute, a schema may be marked for translation by adding it to POTFILES.in, assuming gettext 0.19 is in use (the preferred method for translation):
Alternatively, if intltool 0.50.1 is in use:
GSettings will use gettext to look up translations for the <summary> and <description> elements, and also any <default> elements which have a l10n attribute set. Translations must not be included in the .gschema.xml file by the build system, for example by using intltool XML rules with a .gschema.xml.in template.
If an enumerated type defined in a C header file is to be used in a GSettings schema, it can either be defined manually using an <enum> element in the schema XML, or it can be extracted automatically from the C header. This approach is preferred, as it ensures the two representations are always synchronised. To do so, add the following to the relevant Makefile.am:
gsettings_ENUM_NAMESPACE specifies the schema namespace for the enum files, which are specified in gsettings_ENUM_FILES. This will generate a org.foo.MyApp.enums.xml file containing the extracted enums, which will be automatically included in the schema compilation, install and uninstall rules. It should not be committed to version control or included in EXTRA_DIST.