public abstract class Expression
GtkExpression provides a way to describe references to values.
An important aspect of expressions is that the value can be obtained from a source that is several steps away. For example, an expression may
describe ‘the value of property A of
object1, which is itself the value of a property of
object1 may not even exist yet at the time that the expression is created. This is contrast to GObject property bindings, which can
only create direct connections between the properties of two objects that must both exist for the duration of the binding.
An expression needs to be "evaluated" to obtain the value that it currently refers to. An evaluation always happens in the context of a current object called `this` (it mirrors the behavior of object-oriented languages), which may or may not influence the result of the evaluation. Use evaluate for evaluating an expression.
Various methods for defining expressions exist, from simple constants via ConstantExpression to looking up properties in a Object (even recursively) via PropertyExpression or providing custom functions to transform and combine expressions via ClosureExpression .
Here is an example of a complex expression:
color_expr = gtk_property_expression_new (GTK_TYPE_LIST_ITEM,
expression = gtk_property_expression_new (GTK_TYPE_COLOR,
when evaluated with `this` being a GtkListItem, it will obtain the "item" property from the GtkListItem, and then obtain the "name" property from the resulting object (which is assumed to be of type GTK_TYPE_COLOR).
A more concise way to describe this would be
The most likely place where you will encounter expressions is in the context of list models and list widgets using them. For example, DropDown is evaluating a GtkExpression to obtain strings from the items in its model that it can then use to match against the contents of its search entry. StringFilter is using a GtkExpression for similar reasons.
By default, expressions are not paying attention to changes and evaluation is just a snapshot of the current state at a given time. To get informed about changes, an expression needs to be "watched" via a ExpressionWatch, which will cause a callback to be called whenever the value of the expression may have changed. watch starts watching an expression, and unwatch stops.
GtkExpression in GObject properties
"The expression used by the widget",
When implementing the
GObjectClass.get_property virtual functions, you must use
value_get_expression, to retrieve the stored
Expression from the Value container, and
value_set_expression, to store the Expression
into the Value; for instance:
// in set_property()...
foo_widget_set_expression (foo, gtk_value_get_expression (value));
// in get_property()...
gtk_value_set_expression (value, foo->expression);
GtkExpression in .ui files
GtkBuilder has support for creating expressions. The syntax here can be used where a Expression object is needed like in a <property> tag for an expression property, or in a <binding> tag to bind a property to an expression.
To create an property expression, use the <lookup> element. It can have a `type` attribute to specify the object type, and a `name` attribute to specify the property to look up. The content of <lookup> can either be an element specfiying the expression to use the object, or a string that specifies the name of the object to use.
To create a constant expression, use the <constant> element. If the type attribute is specified, the element content is interpreted as a value of that type. Otherwise, it is assumed to be an object.
<constant type='gchararray'>Hello, world</constant>
To create a closure expression, use the <closure> element. The `type` and `function` attributes specify what function to use for the closure, the content of the element contains the expressions for the parameters.
<closure type='gchararray' function='combine_args_somehow'>
<constant type='gchararray'>File size:</constant>
<lookup type='GFile' name='size'>myfile</lookup>