I just received answer from the kind person who looks after the plugin code now. It seems to be an issue in the legacy code he is trying to improve in the next release. Thanks again very much for pointing out that it is clearly a problem within the plugin.