In doc/plugins.dox:

> +	g_free((gchar *)plugin->info->author);
> +
> +	g_key_file_free(data->file);
> +	g_free(data);
> +}
> +@endcode
> +
> +Finally the demo_proxy's wrapper GeanyPluginFuncs. They are called for each possible sub-plugin and
> +therefore have to multiplex between each using the plugin-defined data pointer. Each is called by
> +Geany as if it were an ordinary, native plugin.
> +
> +proxy_init() actually reads the inferior's file using GKeyFile APIs. It prepares for the help
> +dialog and installs the menu items. proxy_help() is called when the user clicks the help button in
> +the Plugin Manager. Consequently, this fires up a suitable dialog, although with a dummy message.
> +proxy_cleanup() frees all memory allocated in proxy_init().
> +

It isn't clear if the ini file is just something this demo uses to define its sub-plugins, or if its required that all proxies use it, and if so why?

—
Reply to this email directly or view it on GitHub.