Hi Jan, We tested your problem. It is tricky, I think I reproduced the bug in the release 2.1.3. However, it seems we have no such problem in the current build. Tom
↧