Yep, version 1.2.16 seems to have fixed the issue. :)
A zillion thanks, for all the good work.

Reply via email to