Plugin manager does not refresh itself until GTG is restarted

[Bertrand Rousseau]

1/ start GTG
2/ open plugin manager
3/ sport a plugin that cannot be loaded because of missing dependancy
4/ close plugin manager but keep GTG opened
5/ solve the dependancy
6/ re-open plugin manager
7/ the plugin is still amrked has unloadable

This bug is probably caused by the fact that the plugin manager is actually hidden, not destroyed. Adding some kind of reload mechanism should do the trick.

[Lionel Dricot (ploum-deactivatedaccount)]

I think this is mainly fixed in rev. 389. Can you check?

The only exception is when you are removing a package dependencies (such as bugz for the bugzilla plugin). Indeed, as the python library is already loaded, it will works as long as the python program is running.

[Bertrand Rousseau (bertrand-rousseau)]

I still have an issue. For the hamster-plugin for instance, if the service is disabled after the plugin manager has been opened, the plugin is still marked as available even after close and reopening the PM.

[Lionel Dricot (ploum-deactivatedaccount)]

Indeed, once the plugin is loaded, it doesn't do the check anymore.

[Lionel Dricot (ploum-deactivatedaccount)]

Fixed in rev. 395.

Unfortunatly, this will never work with plugins with module dependancies. Indeed, once the module is loaded, it stays in python memory.