https://bugs.kde.org/show_bug.cgi?id=445968
Alvin Wong <al...@alvinhc.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |al...@alvinhc.com
--- Comment #1 from Alvin Wong <al...@alvinhc.com> ---
The workaround that Shotcut uses is not one that we can just go apply it to
every top-level window. I don't think that is the right approach and I don't
think it can even be applied to most dialogs anyway (e.g. those that uses
`QDialog::exec`).
The root cause is probably somewhere in Qt and hard to locate. I suspect it
might have something to do with Qt starting an event loop introducing a delay
to the initial paint event, and because `QDialog::exec` starts an additional
event loop, every dialog opened using this call would show the same behaviour.
If my guess is correct, then this will happen to literally every application
using Qt and it should be reported upstream instead.
--
You are receiving this mail because:
You are watching all bug changes.
