Plugin destruction

[wysota]

The plugin loader can only hold a reference to one instance at a time. If you reuse the same instance of QPluginLoader for many plugins then you are responsible for deleting all the objects yourself.

[paolom]

Ok,
I've correct my code, but the problem is the same:

To call the destructor of the plugin I need to call the unload() function of the QPluginLoader.

Is it an expected behaviour?

[wysota]

You mean that if you do:

QObjectList list;
list << loader.instance();

QObjectList list;
list << loader.instance();

To copy to clipboard, switch view to plain text mode 

and then:

foreach(QObject *o, list) delete o;

foreach(QObject *o, list) delete o;

To copy to clipboard, switch view to plain text mode 

the destructor is not called?

[paolom]

I've a plugin that handle a thread that do some work.
When the app is closed, I want to be sure that this plugin close all the worker thread.
To do this I want to run some code during the closure of the plugin.
At the start I think to do this on the plugin destructor but I test that without unload() the pluginLoader the plugin destructor is not invoked.
On the Qt examples there is not pluginLoader unload() and when the app is closed no plugin destructor is invoked.

My questions:

As your opinion, has any sense to put any code on the plugin destructor, or I need to call another plugin method to do this operation before the plugin is closed??

Does I need to call the unload() function of the pluginLoader?

Which is the safe mode to delete the plugin instances?

Many thanks

[wysota]

When the app is closed, I want to be sure that this plugin close all the worker thread.
To do this I want to run some code during the closure of the plugin.

You shouldn't do that using a destructor but rather a dedicated close() method that each plugin implements and that your plugin handling infrastructure calls before closing the whole system.