Wow, that looks worse than what I came up with. Maybe this doesn't happen on Linux, I can see that there could be differences in this kind of behavior between Windows and Linux. So it looks to me as if 3.3.5 doesn't fix that problem.
The question is if this is a Qt bug or if there is something that can be done on an API level to fix this problem. I have been looking into the setTranslationMode() function but both Point and Area have the same result.

I'm surprised this has reported this problem before...


Thanks,
Thomas