In the case that symbols are not explicitly added; GTK will uses
gmodule.module_.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 function names given in the interface description with
symbols in the application.
A gtk.builder_scope.BuilderScope implementation for the C language.
gtk.builder_cscope.BuilderCScope instances use symbols explicitly added to @builder with prior calls to gtk.builder_cscope.BuilderCScope.addCallbackSymbol. 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.module_.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 function names given in the interface description with symbols in the application.
Note that unless gtk.builder_cscope.BuilderCScope.addCallbackSymbol is called for all signal callbacks which are referenced by the loaded XML, this functionality will require that gmodule.module_.Module be supported on the platform.