summaryrefslogtreecommitdiffstats
path: root/tests/auto/qrect
diff options
context:
space:
mode:
authorThiago Macieira <thiago.macieira@nokia.com>2011-01-27 10:49:49 (GMT)
committerThiago Macieira <thiago.macieira@nokia.com>2011-01-27 13:57:43 (GMT)
commit2e72a8b19ea6c674fb4777860dac50faa5d387e6 (patch)
treee5c684f88671eee9a09a83e7374c1227d7d577ac /tests/auto/qrect
parentbd6c9225328b6042ff14dfddb28e2e1279ba0e46 (diff)
downloadQt-2e72a8b19ea6c674fb4777860dac50faa5d387e6.zip
Qt-2e72a8b19ea6c674fb4777860dac50faa5d387e6.tar.gz
Qt-2e72a8b19ea6c674fb4777860dac50faa5d387e6.tar.bz2
Restore Qt 4.6 behaviour: exec() always enters the event loop.
In Qt 4.6 as well as 4.7's QCoreApplication and QEventLoop, calling exec() always enters the event loop, even if you had tried to quit()/exit() it before entering, with one exception (noted in the unit tests; this difference has been in Qt since at least Qt 4.2). Add unit tests to ensure all of the three classes have the same behaviour. Decide if we want to match the behaviours in Qt 4.8. Reviewed-by: Bradley T. Hughes
Diffstat (limited to 'tests/auto/qrect')
0 files changed, 0 insertions, 0 deletions