-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
style_dialog_optimization #19146
style_dialog_optimization #19146
Conversation
c21f905
to
636ca45
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This solution seems good to me; especially since those QDialog dialogs will be replaced by QML at some point, I think we shouldn't spend too much time on them.
However, I do wonder why it was no problem in MS3. There, nothing was done about disabling accessibility. Do you have any idea about that?
And might there be a way to apply this fix for other dialogs automatically too, like detecting whether an event comes from a dialog that is not opened yet? (Probably not necessary though, because the style dialog is by far the biggest one, so the problem is probably not significant for other dialogs)
This is most likely a consequence of the fact that we are using our custom accessibility root object (see AccessibilityController::init()) and the default is QApplication (which was used in MS3)
I'm leaning toward not applying this fix to other dialogs for now. Implementing automatic detection of whether events need to be ignored would be quite problematic (especially because we have to start ignoring them before calling setupUi) |
I can confirm that this PR fixes the issue for me, similar to the earlier change one you asked be to test, but as far as I can tell without the bad side effects on accessibilty |
If we were to investigate using this elsewhere, there are three places in particular where people have reported issues with lag and it might turn out to be for the same reason:
I also wonder if explicitly disabling accessibility might be a workaround for now (obviously, not for screen reader users). But I only know how to do that on Linux, and I don't experience the issue there. |
Resolves: #13193
Resolves: #13104
Resolves: #17060
Caused by dca87eb