Hi, although we were not able to reproduce this problem, we looked at the provided call stack. It should be fixed in the next release. We would appreciate if you informed us then whether the problem is gone. Tom
↧