Optionalproperties: Partial<Gtk.Builder.ConstructorProps>Internal$signalsCompile-time signal type information.
This instance property is generated only for TypeScript type checking. It is not defined at runtime and should not be accessed in JS code.
Static$gtypeSince 2.12translation_The translation domain used when translating property values that
have been marked as translatable in interface descriptions.
If the translation domain is null, Gtk.Builder uses gettext(),
otherwise g_dgettext().
Since 2.12translationThe translation domain used when translating property values that
have been marked as translatable in interface descriptions.
If the translation domain is null, Gtk.Builder uses gettext(),
otherwise g_dgettext().
Adds the callback_symbol to the scope of builder under the given callback_name.
Using this function overrides the behavior of gtk_builder_connect_signals()
for any callback symbols that are added. Using this method allows for better
encapsulation as it does not require that callback symbols be declared in
the global namespace.
Parses a file containing a [GtkBuilder UI definition][BUILDER-UI]
and merges it with the current contents of builder.
Most users will probably want to use gtk_builder_new_from_file().
If an error occurs, 0 will be returned and error will be assigned a
GLib.Error from the #GTK_BUILDER_ERROR, #G_MARKUP_ERROR or #G_FILE_ERROR
domain.
It’s not really reasonable to attempt to handle failures of this
call. You should not use this function with untrusted files (ie:
files that are not part of your application). Broken Gtk.Builder
files can easily crash your program, and it’s possible that memory
was leaked leading up to the reported failure. The only reasonable
thing to do when an error is detected is to call g_error().
the name of the file to parse
A positive value on success, 0 if an error occurred
Parses a resource file containing a [GtkBuilder UI definition][BUILDER-UI]
and merges it with the current contents of builder.
Most users will probably want to use gtk_builder_new_from_resource().
If an error occurs, 0 will be returned and error will be assigned a
GLib.Error from the #GTK_BUILDER_ERROR, #G_MARKUP_ERROR or #G_RESOURCE_ERROR
domain.
It’s not really reasonable to attempt to handle failures of this
call. The only reasonable thing to do when an error is detected is
to call g_error().
the path of the resource file to parse
A positive value on success, 0 if an error occurred
Parses a string containing a [GtkBuilder UI definition][BUILDER-UI]
and merges it with the current contents of builder.
Most users will probably want to use gtk_builder_new_from_string().
Upon errors 0 will be returned and error will be assigned a
GLib.Error from the #GTK_BUILDER_ERROR, #G_MARKUP_ERROR or
#G_VARIANT_PARSE_ERROR domain.
It’s not really reasonable to attempt to handle failures of this
call. The only reasonable thing to do when an error is detected is
to call g_error().
the string to parse
the length of buffer (may be -1 if buffer is nul-terminated)
A positive value on success, 0 if an error occurred
Parses a file containing a [GtkBuilder UI definition][BUILDER-UI]
building only the requested objects and merges
them with the current contents of builder.
Upon errors 0 will be returned and error will be assigned a
GLib.Error from the #GTK_BUILDER_ERROR, #G_MARKUP_ERROR or #G_FILE_ERROR
domain.
If you are adding an object that depends on an object that is not
its child (for instance a Gtk.TreeView that depends on its
Gtk.TreeModel), you have to explicitly list all of them in object_ids.
the name of the file to parse
nul-terminated array of objects to build
A positive value on success, 0 if an error occurred
Parses a resource file containing a [GtkBuilder UI definition][BUILDER-UI]
building only the requested objects and merges
them with the current contents of builder.
Upon errors 0 will be returned and error will be assigned a
GLib.Error from the #GTK_BUILDER_ERROR, #G_MARKUP_ERROR or #G_RESOURCE_ERROR
domain.
If you are adding an object that depends on an object that is not
its child (for instance a Gtk.TreeView that depends on its
Gtk.TreeModel), you have to explicitly list all of them in object_ids.
the path of the resource file to parse
nul-terminated array of objects to build
A positive value on success, 0 if an error occurred
Parses a string containing a [GtkBuilder UI definition][BUILDER-UI]
building only the requested objects and merges
them with the current contents of builder.
Upon errors 0 will be returned and error will be assigned a
GLib.Error from the #GTK_BUILDER_ERROR or #G_MARKUP_ERROR domain.
If you are adding an object that depends on an object that is not
its child (for instance a Gtk.TreeView that depends on its
Gtk.TreeModel), you have to explicitly list all of them in object_ids.
the string to parse
the length of buffer (may be -1 if buffer is nul-terminated)
nul-terminated array of objects to build
A positive value on success, 0 if an error occurred
SignalconnectSignalconnect_This method is a simpler variation of gtk_builder_connect_signals_full().
It uses symbols explicitly added to builder with prior calls to
gtk_builder_add_callback_symbol(). In the case that symbols are not
explicitly added; it uses GModule.Module’s introspective features (by opening the module null)
to look at the application’s symbol table. From here it tries to match
the signal handler names given in the interface description with
symbols in the application and connects the signals. Note that this
function can only be called once, subsequent calls will do nothing.
Note that unless gtk_builder_add_callback_symbol() is called for
all signal callbacks which are referenced by the loaded XML, this
function will require that GModule.Module be supported on the platform.
If you rely on GModule.Module support to lookup callbacks in the symbol table, the following details should be noted:
When compiling applications for Windows, you must declare signal callbacks with #G_MODULE_EXPORT, or they will not be put in the symbol table. On Linux and Unices, this is not necessary; applications should instead be compiled with the -Wl,--export-dynamic CFLAGS, and linked against gmodule-export-2.0.
Optionaluser_data: anyuser data to pass back with all signals
This function can be thought of the interpreted language binding
version of gtk_builder_connect_signals(), except that it does not
require GModule to function correctly.
the function used to connect the signals
SignalemitMain private entry point for building composite container components from template XML.
This is exported purely to let gtk-builder-tool validate templates, applications have no need to call this function.
A positive value on success, 0 if an error occurred
Gets the Gtk.Application associated with the builder.
The Gtk.Application is used for creating action proxies as requested from XML that the builder is loading.
By default, the builder uses the default application: the one from
g_application_get_default(). If you want to use another application
for constructing proxies, use gtk_builder_set_application().
the application being used by the builder, or null
Gets all objects that have been constructed by builder. Note that
this function does not increment the reference counts of the returned
objects.
a newly-allocated GLib.SList containing all the objects constructed by the Gtk.Builder instance. It should be freed by g_slist_free()
Gets the translation domain of builder.
the translation domain. This string is owned by the builder object and must not be modified or freed.
Looks up a type by name, using the virtual function that Gtk.Builder has for that purpose. This is mainly used when implementing the Gtk.Buildable interface on a type.
type name to lookup
the GObject.GType found for type_name or #G_TYPE_INVALID if no type was found
Sets the application associated with builder.
You only need this function if there is more than one Gio.Application
in your process. application cannot be null.
Sets the translation domain of builder.
See Gtk.Builder.translation_domain.
Optionaldomain: stringthe translation domain or null
This function demarshals a value from a string. This function
calls g_value_init() on the value argument, so it need not be
initialised beforehand.
This function can handle char, uchar, boolean, int, uint, long, ulong, enum, flags, float, double, string, Gdk.Color, Gdk.RGBA and Gtk.Adjustment type values. Support for Gtk.Widget type values is still to come.
Upon errors false will be returned and error will be assigned a
GLib.Error from the #GTK_BUILDER_ERROR domain.
the GObject.ParamSpec for the property
the string representation of the value
true on success
Like gtk_builder_value_from_string(), this function demarshals
a value from a string, but takes a GObject.GType instead of GObject.ParamSpec.
This function calls g_value_init() on the value argument, so it
need not be initialised beforehand.
Upon errors false will be returned and error will be assigned a
GLib.Error from the #GTK_BUILDER_ERROR domain.
the GObject.GType of the value
the string representation of the value
true on success
Virtualvfunc_Looks up a type by name, using the virtual function that Gtk.Builder has for that purpose. This is mainly used when implementing the Gtk.Buildable interface on a type.
type name to lookup
StaticnewStaticnew_Staticnew_Staticnew_Creates a binding between source_property on source and target_property
on target.
Whenever the source_property is changed the target_property is
updated using the same value. For instance:
g_object_bind_property (action, "active", widget, "sensitive", 0);
Will result in the "sensitive" property of the widget GObject.Object instance to be updated with the same value of the "active" property of the action GObject.Object instance.
If flags contains GObject.BindingFlags.BIDIRECTIONAL then the binding will be mutual:
if target_property on target changes then the source_property on source
will be updated as well.
The binding will automatically be removed when either the source or the
target instances are finalized. To remove the binding without affecting the
source and the target you can just call g_object_unref() on the returned
GObject.Binding instance.
Removing the binding by calling g_object_unref() on it must only be done if
the binding, source and target are only used from a single thread and it
is clear that both source and target outlive the binding. Especially it
is not safe to rely on this if the binding, source or target can be
finalized from different threads. Keep another reference to the binding and
use g_binding_unbind() instead to be on the safe side.
A GObject.Object can have multiple bindings.
the property on source to bind
the target GObject.Object
the property on target to bind
flags to pass to GObject.Binding
the GObject.Binding instance representing the binding between the two GObject.Object instances. The binding is released whenever the GObject.Binding reference count reaches zero.
Complete version of g_object_bind_property().
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.
If flags contains GObject.BindingFlags.BIDIRECTIONAL then the binding will be mutual:
if target_property on target changes then the source_property on source
will be updated as well. The transform_from function is only used in case
of bidirectional bindings, otherwise it will be ignored
The binding will automatically be removed when either the source or the
target instances are finalized. This will release the reference that is
being held on the GObject.Binding instance; if you want to hold on to the
GObject.Binding instance, you will need to hold a reference to it.
To remove the binding, call g_binding_unbind().
A GObject.Object can have multiple bindings.
The same user_data parameter will be used for both transform_to
and transform_from transformation functions; the notify function will
be called once, when the binding is removed. If you need different data
for each transformation function, please use
g_object_bind_property_with_closures() instead.
the property on source to bind
the target GObject.Object
the property on target to bind
flags to pass to GObject.Binding
Optionaltransform_to: BindingTransformFuncthe transformation function from the source to the target, or null to use the default
Optionaltransform_from: BindingTransformFuncthe transformation function from the target to the source, or null to use the default
Optionalnotify: DestroyNotifya function to call when disposing the binding, to free resources used by the transformation functions, or null if not required
the GObject.Binding instance representing the binding between the two GObject.Object instances. The binding is released whenever the GObject.Binding reference count reaches zero.
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 the language bindings friendly version of
g_object_bind_property_full(), using GClosures instead of
function pointers.
the property on source to bind
the target GObject.Object
the property on target to bind
flags to pass to GObject.Binding
a GObject.Closure wrapping the transformation function from the source to the target, or null to use the default
a GObject.Closure wrapping the transformation function from the target to the source, or null to use the default
the GObject.Binding instance representing the binding between the two GObject.Object instances. The binding is released whenever the GObject.Binding reference count reaches zero.
Blocks a handler of an instance so it will not be called during any signal emissions
Handler ID of the handler to be blocked
Disconnects a handler from an instance so it will not be called during any future or currently ongoing emissions of the signal it has been connected to.
Handler ID of the handler to be disconnected
This function is intended for GObject.Object 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 g_object_ref_sink().
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.Object::notify signal is emitted for each property modified while the
object is frozen.
This is necessary for accessors that modify multiple properties to prevent premature notification while the object is still being modified.
Gets a named field from the objects table of associations (see g_object_set_data()).
name of the key for that association
the data if found, or null if no such data exists.
Gets a property of an object.
The value can be:
In general, a copy is made of the property contents and the caller is responsible for freeing the memory by calling GObject.Value.unset.
Note that GObject.Object.get_property is really intended for language bindings, GObject.Object.get is much more convenient for C programming.
The name of the property to get
Return location for the property value. Can be an empty GObject.Value initialized by G_VALUE_INIT (auto-initialized with expected type since GLib 2.60), a GObject.Value initialized with the expected property type, or a GObject.Value initialized with a transformable type
This function gets back user data pointers stored via
g_object_set_qdata().
A GLib.Quark, naming the user data pointer
The user data pointer set, or null
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.
the names of each property to get
the values of each property to get
Checks whether object has a [floating][floating-ref] reference.
true if object has a floating reference
Emits a "notify" signal for the property property_name on object.
When possible, eg. when signaling a property change from within the class
that registered the property, you should use g_object_notify_by_pspec()
instead.
Note that emission of the notify signal may be blocked with
g_object_freeze_notify(). In this case, the signal emissions are queued
and will be emitted (in reverse order) when g_object_thaw_notify() is
called.
the name of a property installed on the class of object.
Emits a "notify" signal for the property specified by pspec on object.
This function omits the property name lookup, hence it is faster than
g_object_notify().
One way to avoid using g_object_notify() from within the
class that registered the properties, and using g_object_notify_by_pspec()
instead, is to store the GParamSpec used with
g_object_class_install_property() inside a static array, e.g.:
typedef enum
{
PROP_FOO = 1,
PROP_LAST
} MyObjectProperty;
static GParamSpec *properties[PROP_LAST];
static void
my_object_class_init (MyObjectClass *klass)
{
properties[PROP_FOO] = g_param_spec_int ("foo", NULL, NULL,
0, 100,
50,
G_PARAM_READWRITE | G_PARAM_STATIC_STRINGS);
g_object_class_install_property (gobject_class,
PROP_FOO,
properties[PROP_FOO]);
}
and then notify a change on the "foo" property with:
g_object_notify_by_pspec (self, properties[PROP_FOO]);
the GObject.ParamSpec of a property installed on the class of object.
Increases the reference count of object.
Since GLib 2.56, if GLIB_VERSION_MAX_ALLOWED is 2.56 or greater, the type
of object will be propagated to the return type (using the GCC typeof()
extension), so any casting the caller needs to do on the return type must be
explicit.
the same object
Increase the reference count of object, and possibly remove the
[floating][floating-ref] reference, if object has a floating reference.
In other words, if the object is floating, then this call "assumes ownership" of the floating reference, converting it to a normal reference by clearing the floating flag while leaving the reference count unchanged. If the object is not floating, then this call adds a new normal reference increasing the reference count by one.
Since GLib 2.56, the type of object will be propagated to the return type
under the same conditions as for g_object_ref().
object
Releases all references to other objects. This can be used to break reference cycles.
This function should only be called from object system implementations.
Sets multiple properties of an object at once. The properties argument should be a dictionary mapping property names to values.
Object containing the properties to set
Each object carries around a table of associations from strings to pointers. This function lets you set an association.
If the object already had an association with that name, the old association will be destroyed.
Internally, the key is converted to a GLib.Quark using g_quark_from_string().
This means a copy of key is kept permanently (even after object has been
finalized) — so it is recommended to only use a small, bounded set of values
for key in your program, to avoid the GLib.Quark storage growing unbounded.
name of the key
Optionaldata: anydata to associate with that key
Sets a property on an object.
The name of the property to set
The value to set the property to
Remove a specified datum from the object's data associations, without invoking the association's destroy handler.
name of the key
the data if found, or null if no such data exists.
This function gets back user data pointers stored via
g_object_set_qdata() 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:
void
object_add_to_user_list (GObject *object,
const gchar *new_string)
{
// the quark, naming the object data
GQuark quark_string_list = g_quark_from_static_string ("my-string-list");
// retrieve the old string list
GList *list = g_object_steal_qdata (object, quark_string_list);
// prepend new string
list = g_list_prepend (list, g_strdup (new_string));
// this changed 'list', so we need to set it again
g_object_set_qdata_full (object, quark_string_list, list, free_string_list);
}
static void
free_string_list (gpointer data)
{
GList *node, *list = data;
for (node = list; node; node = node->next)
g_free (node->data);
g_list_free (list);
}
Using g_object_get_qdata() in the above example, instead of
g_object_steal_qdata() would have left the destroy function set,
and thus the partial string list would have been freed upon
g_object_set_qdata_full().
A GLib.Quark, naming the user data pointer
The user data pointer set, or null
Stops a signal's emission by the given signal name. This will prevent the default handler and any subsequent signal handlers from being invoked.
Name of the signal to stop emission of
Reverts the effect of a previous call to
g_object_freeze_notify(). The freeze count is decreased on object
and when it reaches zero, queued "notify" signals are emitted.
Duplicate notifications for each property are squashed so that at most one GObject.Object::notify signal is emitted for each property, in the reverse order in which they have been queued.
It is an error to call this function when the freeze count is zero.
Unblocks a handler so it will be called again during any signal emissions
Handler ID of the handler to be unblocked
Decreases the reference count of object. When its reference count
drops to 0, the object is finalized (i.e. its memory is freed).
If the pointer to the GObject.Object may be reused in future (for example, if it is
an instance variable of another object), it is recommended to clear the
pointer to null rather than retain a dangling pointer to a potentially
invalid GObject.Object instance. Use g_clear_object() for this.
Virtualvfunc_the constructed function is called by g_object_new() as the
final step of the object creation process. At the point of the call, all
construction properties have been set on the object. The purpose of this
call is to allow for object initialisation steps that can only be performed
after construction properties have been set. constructed implementors
should chain up to the constructed call of their parent class to allow it
to complete its initialisation.
Virtualvfunc_Virtualvfunc_the dispose function is supposed to drop all references to other
objects, but keep the instance otherwise intact, so that client method
invocations still work. It may be run multiple times (due to reference
loops). Before returning, dispose should chain up to the dispose method
of the parent class.
Virtualvfunc_instance finalization function, should finish the finalization of
the instance begun in dispose and chain up to the finalize method of the
parent class.
Virtualvfunc_Virtualvfunc_Emits a "notify" signal for the property property_name on object.
When possible, eg. when signaling a property change from within the class
that registered the property, you should use g_object_notify_by_pspec()
instead.
Note that emission of the notify signal may be blocked with
g_object_freeze_notify(). In this case, the signal emissions are queued
and will be emitted (in reverse order) when g_object_thaw_notify() is
called.
Virtualvfunc_the generic setter for all properties of this type. Should be
overridden for every type with properties. If implementations of
set_property don't emit property change notification explicitly, this will
be done implicitly by the type system. However, if the notify signal is
emitted explicitly, the type system will not emit it a second time.
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 g_closure_invalidate() on
it, in order to prevent invocations of the closure with a finalized
(nonexisting) object. Also, g_object_ref() and g_object_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.
GObject.Closure to watch
Static_Staticcompat_Optionaldata: anyStaticfind_Staticinstall_Staticinstall_the id for the new property
the GObject.ParamSpec for the new property
Staticinterface_Find the GObject.ParamSpec with the given name for an
interface. Generally, the interface vtable passed in as g_iface
will be the default vtable from g_type_default_interface_ref(), or,
if you know the interface has already been loaded,
g_type_default_interface_peek().
any interface vtable for the interface, or the default vtable for the interface
name of a property to look up.
Staticinterface_Add a property to an interface; this is only useful for interfaces
that are added to GObject-derived types. Adding a property to an
interface forces all objects classes with that interface to have a
compatible property. The compatible property could be a newly
created GObject.ParamSpec, but normally
g_object_class_override_property() will be used so that the object
class only needs to provide an implementation and inherits the
property description, default value, bounds, and so forth from the
interface property.
This function is meant to be called from the interface's default
vtable initialization function (the class_init member of
GObject.TypeInfo.) It must not be called after after class_init has
been called for any object types implementing this interface.
If pspec is a floating reference, it will be consumed.
any interface vtable for the interface, or the default vtable for the interface.
the GObject.ParamSpec for the new property
Staticinterface_Lists the properties of an interface.Generally, the interface
vtable passed in as g_iface will be the default vtable from
g_type_default_interface_ref(), or, if you know the interface has
already been loaded, g_type_default_interface_peek().
any interface vtable for the interface, or the default vtable for the interface
Staticlist_StaticnewvStaticoverride_the new property ID
the name of a property registered in a parent class or in an interface of this class.
A GtkBuilder is an auxiliary object that reads textual descriptions of a user interface and instantiates the described objects. To create a GtkBuilder from a user interface description, call
gtk_builder_new_from_file(),gtk_builder_new_from_resource()orgtk_builder_new_from_string().In the (unusual) case that you want to add user interface descriptions from multiple sources to the same GtkBuilder you can call
gtk_builder_new()to get an empty builder and populate it by (multiple) calls togtk_builder_add_from_file(),gtk_builder_add_from_resource()orgtk_builder_add_from_string().A GtkBuilder holds a reference to all objects that it has constructed and drops these references when it is finalized. This finalization can cause the destruction of non-widget objects or widgets which are not contained in a toplevel window. For toplevel windows constructed by a builder, it is the responsibility of the user to call
gtk_widget_destroy()to get rid of them and all the widgets they contain.The functions
gtk_builder_get_object()andgtk_builder_get_objects()can be used to access the widgets in the interface by the names assigned to them inside the UI description. Toplevel windows returned by these functions will stay around until the user explicitly destroys them withgtk_widget_destroy(). Other widgets will either be part of a larger hierarchy constructed by the builder (in which case you should not have to worry about their lifecycle), or without a parent, in which case they have to be added to some container to make use of them. Non-widget objects need to be reffed withg_object_ref()to keep them beyond the lifespan of the builder.The function
gtk_builder_connect_signals()and variants thereof can be used to connect handlers to the named signals in the description.GtkBuilder UI Definitions # {
BUILDER-UI}GtkBuilder parses textual descriptions of user interfaces which are specified in an XML format which can be roughly described by the RELAX NG schema below. We refer to these descriptions as “GtkBuilder UI definitions” or just “UI definitions” if the context is clear. Do not confuse GtkBuilder UI Definitions with [GtkUIManager UI Definitions][XML-UI], which are more limited in scope. It is common to use
.uias the filename extension for files containing GtkBuilder UI definitions.RELAX NG Compact Syntax
The toplevel element is
<interface>. It optionally takes a “domain” attribute, which will make the builder look for translated strings usingdgettext()in the domain specified. This can also be done by callinggtk_builder_set_translation_domain()on the builder. Objects are described by<object>elements, which can contain<property>elements to set properties,<signal>elements which connect signals to handlers, and<child>elements, which describe child objects (most often widgets inside a container, but also e.g. actions in an action group, or columns in a tree model). A<child>element contains an<object>element which describes the child object. The target toolkit version(s) are described by<requires>elements, the “lib” attribute specifies the widget library in question (currently the only supported value is “gtk+”) and the “version” attribute specifies the target version in the form<major>.<minor>. The builder will error out if the version requirements are not met.Typically, the specific kind of object represented by an
<object>element is specified by the “class” attribute. If the type has not been loaded yet, GTK+ tries to find theget_type()function from the class name by applying heuristics. This works in most cases, but if necessary, it is possible to specify the name of theget_type()function explictly with the "type-func" attribute. As a special case, GtkBuilder allows to use an object that has been constructed by a Gtk.UIManager in another part of the UI definition by specifying the id of the Gtk.UIManager in the “constructor” attribute and the name of the object in the “id” attribute.Objects may be given a name with the “id” attribute, which allows the application to retrieve them from the builder with
gtk_builder_get_object(). An id is also necessary to use the object as property value in other parts of the UI definition. GTK+ reserves ids starting and ending with___(3 underscores) for its own purposes.Setting properties of objects is pretty straightforward with the
<property>element: the “name” attribute specifies the name of the property, and the content of the element specifies the value. If the “translatable” attribute is set to a true value, GTK+ usesgettext()(ordgettext()if the builder has a translation domain set) to find a translation for the value. This happens before the value is parsed, so it can be used for properties of any type, but it is probably most useful for string properties. It is also possible to specify a context to disambiguate short strings, and comments which may help the translators.GtkBuilder can parse textual representations for the most common property types: characters, strings, integers, floating-point numbers, booleans (strings like “TRUE”, “t”, “yes”, “y”, “1” are interpreted as
true, strings like “FALSE”, “f”, “no”, “n”, “0” are interpreted asfalse), enumerations (can be specified by their name, nick or integer value), flags (can be specified by their name, nick, integer value, optionally combined with “|”, e.g. “GTK_VISIBLE|GTK_REALIZED”) and colors (in a format understood bygdk_rgba_parse()).GVariants can be specified in the format understood by
g_variant_parse(), and pixbufs can be specified as a filename of an image file to load.Objects can be referred to by their name and by default refer to objects declared in the local xml fragment and objects exposed via
gtk_builder_expose_object(). In general, GtkBuilder allows forward references to objects — declared in the local xml; an object doesn’t have to be constructed before it can be referred to. The exception to this rule is that an object has to be constructed before it can be used as the value of a construct-only property.It is also possible to bind a property value to another object's property value using the attributes "bind-source" to specify the source object of the binding, "bind-property" to specify the source property and optionally "bind-flags" to specify the binding flags. Internally builder implements this using GBinding objects. For more information see
g_object_bind_property()Signal handlers are set up with the
<signal>element. The “name” attribute specifies the name of the signal, and the “handler” attribute specifies the function to connect to the signal. By default, GTK+ tries to find the handler usingg_module_symbol(), but this can be changed by passing a custom Gtk.BuilderConnectFunc togtk_builder_connect_signals_full(). The remaining attributes, “after”, “swapped” and “object”, have the same meaning as the corresponding parameters of theg_signal_connect_object()org_signal_connect_data()functions. A “last_modification_time” attribute is also allowed, but it does not have a meaning to the builder.Sometimes it is necessary to refer to widgets which have implicitly been constructed by GTK+ as part of a composite widget, to set properties on them or to add further children (e.g. the
vboxof a Gtk.Dialog). This can be achieved by setting the “internal-child” property of the<child>element to a true value. Note that GtkBuilder still requires an<object>element for the internal child, even if it has already been constructed.A number of widgets have different places where a child can be added (e.g. tabs vs. page content in notebooks). This can be reflected in a UI definition by specifying the “type” attribute on a
<child>The possible values for the “type” attribute are described in the sections describing the widget-specific portions of UI definitions.A GtkBuilder UI Definition
Beyond this general structure, several object classes define their own XML DTD fragments for filling in the ANY placeholders in the DTD above. Note that a custom element in a
<child>element gets parsed by the custom tag handler of the parent object, while a custom element in an<object>element gets parsed by the custom tag handler of the object.These XML fragments are explained in the documentation of the respective objects.
Additionally, since 3.10 a special
<template>tag has been added to the format allowing one to define a widget class’s components. See the [GtkWidget documentation][composite-templates] for details.