foxin12 Thank you for showing us the video. Indeed, I was able to reproduce the problem in 4.2.42, and when I reverted to 4.2.40, the bug did not occur, so it seems to be a bug caused by the latest update. We would like to address this issue as soon as possible. However, if it is currently interfering with your work, please revert to version 4.2.40.