GNOME Bugzilla – Bug 752662
registry: Add plugins to the registry we are loading and not default one
Last modified: 2015-08-16 13:38:42 UTC
When running gst_registry_scan_plugin_file we were losing the information about the registry being loaded and ended up adding the plugin to the default registry which was not correct.
Created attachment 307824 [details] [review] registry: Add plugins to the registry we are loading and not default one
How are you using a non-default registry? The intention was to make the registry a singleton really, even if we clearly don't enforce that at the moment so you can still get around it using g_object_new() etc.
We have a dedicated registry for GstValidate plugins. The API makes clear that it is possible, and it works just fine. Though without that little patch we could not list_plugins from that dedicated registry.
Comment on attachment 307824 [details] [review] registry: Add plugins to the registry we are loading and not default one Patch is obviously correct. Perhaps you could rename the func to _load_file_for_registry() or something, to make the difference/function clearer.
Attachment 307824 [details] pushed as 749810b - registry: Add plugins to the registry we are loading and not default one
I've renamed as suggested.