Sorry for late reply. We have fixed the bug you mentioned. It will be applied to the next version.