public interface BuilderScope : Object
The primary intended audience is bindings that want to provide deeper integration of Builder into the language.
A BuilderScope instance may be used with multiple Builder objects, even at once.
By default, GTK will use its own implementation of BuilderScope for the C language which can be created via BuilderCScope.
BuilderCScope instances use symbols explicitly added to
prior calls to add_callback_symbol. If developers want to do that,
they are encouraged to create their own scopes for that purpose.
In the case that symbols are not explicitly added; GTK will uses
GModule’s introspective features (by opening the module
null) to look at the application’s symbol table. From here it tries to match the signal function names given
in the interface description with symbols in the application.
Note that unless add_callback_symbol is called for all signal
callbacks which are referenced by the loaded XML, this functionality will require that
GModule be supported on the platform.