diff options
| author | Kai Koehne <kai.koehne@nokia.com> | 2011-09-29 10:12:15 (GMT) |
|---|---|---|
| committer | Kai Koehne <kai.koehne@nokia.com> | 2011-09-29 13:21:43 (GMT) |
| commit | 739e705150ad114eb92a1fac34a51d30322ffc31 (patch) | |
| tree | 5f121ac2c6414ff6587fd1dd45f48ab11751a85b /src/gui/text/qfontengine_ft.cpp | |
| parent | 2a1e6ef9d3f519d9109672b593dae07821e1c043 (diff) | |
| download | Qt-739e705150ad114eb92a1fac34a51d30322ffc31.zip Qt-739e705150ad114eb92a1fac34a51d30322ffc31.tar.gz Qt-739e705150ad114eb92a1fac34a51d30322ffc31.tar.bz2 | |
QDeclarativeDebug: Fix autotest breakage in qdeclarativedebugjs
In case a service is waiting for messages via waitForMessage, deliver
all arriving messages to the service directly, not only the first one.
In the case of QDeclarativeDebugJS::watchExpressions() test case,
the first message is actually WATCH_EXPRESSIONS , followed by
BREAKPOINTS. However, the second BREAKPOINTS command wasn't
delivered directly, but queued in the main event loop. As soon as
waitForMessage() was returning, QJSDebugClient was just calling
waitForMessage() anew (because BREAKPOINTS wasn't delivered yet),
blocking the main event loop from being run.
Reviewed-by: Aurindam Jana
Diffstat (limited to 'src/gui/text/qfontengine_ft.cpp')
0 files changed, 0 insertions, 0 deletions