Thanks Keet for reporting this issue. I fixed it and the correction will be available in the next version.