Hello Adam,

thanks for the hint! The upcoming v1.7 release (or candidate) will include a 
fix for this problem.

With regards,
Matthias

Reply via email to