I just checked and this issue is still present in 0.83.
Is there any progress on the Qt bug fixing?
Which is the specific bug, we could just vote for it to make fixing higher priority

Best,
András
Thank you for the reply!xnview wrote:it's a problem with QT API, i wait a fix