When a method with the same name is found, then 'Event' is added to the signal's name. It seems that in most cases the method name should be preferred over the signal name. Also emit a warning tag, when a method is renamed, because these events should be renamed using the metafile manually.
Method was missing the proper return type which generated the Ref method but did not pass the check for the special Ref method handling in the generator. Also mark these return types as owned
This allows an easier integration with the generator because array and length params are double-linked
…he same name
When having more namespaces in a gir document there could be types which have the same name but in different namespaces. In this case the wrong type might be used. So only use the ancestors of the current type, which also speeds up the binding process.
…he type system using reflection
Sometimes it's easier to fix things before converting to gapi
Fundamental types can be treated as opaque.
Using abstract classes in bindings results in ConstructorNotFound exceptions in GLib, because abstract classes are skipped when searching for an appropriate constructor. So rather than making these classes abstract, mark the default constructor as protected so it can be instantiated from GLib.
After some testing it seems that this is not needed anymore. It might had been related to a wrong element order in the output which is fixed for some time.
--merge-with takes a comma seperated list of girs, which will get merged into a temporary gir file containing all namespaces, which will then be converted by gir2gapi
Removed redundant callbacks from field/callbacks, which are already covered by virtual_methods
Gapi needs to resolve some types from other libraries, additional includes can be added using the -I commandline parameter or adding a <include xml="PATH/TO/XML"/> in the api file (throughmetadata patching)