This method is a simpler variation of Builder.connectSignalsFull. It uses symbols explicitly added to builder with prior calls to Builder.addCallbackSymbol. In the case that symbols are not explicitly added; it uses glib.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 Builder.addCallbackSymbol is called for all signal callbacks which are referenced by the loaded XML, this function will require that glib.Module be supported on the platform.

If you rely on glib.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.

class Builder
void* userData


userData void*

user data to pass back with all signals