We have released a fix for this issue in version 2.0.4. We warmly invite you to join our improvement programme and try the latest version. Your feedback would be greatly appreciated.