| commit | 55e6be0e4816d65c0611e0b54bfdba059a52c9b5 | |
| author | Hugo Beauzée-Luyssen <hugo@beauzee.fr> | |
| Fri, 9 Feb 2018 14:47:05 +0000 (9 15:47 +0100) | ||
| committer | Hugo Beauzée-Luyssen <hugo@beauzee.fr> | |
| Fri, 9 Feb 2018 14:58:29 +0000 (9 15:58 +0100) | ||
| tree | d3ea42c0db326216d2e087dc71be69c3f3cbf2f1 | treesnapshot (tar.gz zip) |
| parent | eadc1bda44ca41705d76f477b031bc3d788e2b51 | commitdiff |
qt: Don't display progress dialog as modal
Updating the dialog will call processEvents, which could end up
processing another dialog progress update, calling the event loop again,
and so on until we stack overflow.
Basically, having a modal progress dialog means that any user of that
API could potentially cause stack overflows if update calls were to be
unpaced.
Part #2 of fixing #18640 and #17060
Updating the dialog will call processEvents, which could end up
processing another dialog progress update, calling the event loop again,
and so on until we stack overflow.
Basically, having a modal progress dialog means that any user of that
API could potentially cause stack overflows if update calls were to be
unpaced.
Part #2 of fixing #18640 and #17060
| modules/gui/qt/dialogs/external.cpp | diffblobblamehistory |