Problem solved for me too with version 1.4.2.
And I must thank the developer for his fantastic support from the moment I reported this problem to him. Great work!