[QGIS-Developer] plugin reload fail

[Borys Jurgiel]

Hi,

It's not so straightforward to recursively reload complex plugins, thus both 
Plugin Manager and Plugin Reloader have a long-standing problem with reloading 
modules placed in subdirectories. This is the case of opeNoise, where most of 
the code is in the 'tools' subdirectory, so all changes there require QGIS to 
be restarted.

I've just released Plugin Reloader 0.7.5 that hopefully fixes this issue 
finally. Could you please test if it helps with opeNoise? If so, I'll apply 
the same to the Manager or even qgis.utils.

Unfortunately it's only for QGIS 3, as I didn't success to make it working 
with Python 2 (and the old opeNoise).

Best regards,
Borys


Dnia sobota, 13 października 2018 12:15:28 CEST DelazJ pisze:
> Hi,
> 
> How about reloading with the "Plugin reloader" plugin [0]? You might need
> to enable "show experimental plugins" beforehand.
> I thik this would save QGIS I/O.
> 
> [0] http://plugins.qgis.org/plugins/plugin_reloader/
> 
> Regards,
> Harrissou
> 
> Le sam. 13 oct. 2018 à 10:14, Richard Duivenvoorde <rdmailings at duif.net> a
> 
> écrit :
> > On 10/12/2018 06:20 PM, Ing. Pierluigi De Rosa wrote:
> > > Dear all,
> > > 
> > > I have a simple problem.
> > > I'm porting the opeNoise plugin [1] to 3.x
> > > I'm not the author plugin but I'm experiencing that the plugin reload
> > > fails. It tels me that the plugin have been reloaded but the changes are
> > > non applied. Even if I deactivate and than activate the plugin the same
> > > results (no changes detected).
> > > The only way is to restart the software any time losing too much time.
> > 
> > How sure are you that it is not reloaded?
> > Can you check by writing some message with a version number?
> > 
> > Normally writing the
> > 
> > __init__
> > initGui
> > unload
> > 
> > should be enough. Only thing I could think off is that you do not
> > disconnect the QActions (though I'm not even sure if that is really
> > needed).
> > 
> > Also note that if you reload your plugin AFTER an exception, often you
> > end up with a situation where QGIS still has (parts) of the plugin in
> > memory while also loading a new version of your plugin, so sometimes
> > showing 2 versions of your pluginbutton/toolbar etc. I think only a QGIS
> > restart works then.
> > 
> > Another think I've had is that mixing up an already installed version
> > with the one I'm developing (because the symbolic link was gone, or I
> > was actually working in another profile then I thought or.... other
> > silly things)
> > 
> > Regards,
> > 
> > Richard
> > _______________________________________________
> > QGIS-Developer mailing list
> > QGIS-Developer at lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer