@frank18, I've got that correction available in the plugin's GitHub repository, issue #53. I guess it's time to go forward with v1.0.8!