summaryrefslogtreecommitdiffstats
path: root/tests/benchmarks/corelib/text/qstringlist/main.cpp
diff options
context:
space:
mode:
authorMorten Sørvig <morten.sorvig@qt.io>2021-05-20 13:01:15 +0200
committerTor Arne Vestbø <tor.arne.vestbo@qt.io>2021-06-23 06:57:32 +0000
commit713c2a7af6688b9cecf56a79514bc683273fb2e4 (patch)
tree2c52cf5fc89239a75b5e7cbb49a26fd918e5d79f /tests/benchmarks/corelib/text/qstringlist/main.cpp
parent2e12c2caf5e32a3deda4c01afd96b362748b7c3e (diff)
wasm: remove QEventLoop workaroundsHEADdev
In general, QEventLoop::exec() _can_ be used as-is on WebAssembly, provided that the event dispatcher supports the use case. Use cases that can work include calling exec() on a secondary thread, or calling exec() on the main thread if asyncify is used. Some use cases will still require special casing for Wasm, such as the non-asyncified QApplication::exec(), but that can be handles closer to where the workarounds needed, for example in QApplication. This removes the partial support for nested event loops on the main thread, which did not really work. Also, we no longer call emscripten_force_exit() on QEvetLoop::exit(), which makes it possible to exit a top-level event loop without exiting the process. Task-number: QTBUG-70185 Change-Id: I3a28f41b8547ed3ba1bdf6a835e6662483e34449 Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io> Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
Diffstat (limited to 'tests/benchmarks/corelib/text/qstringlist/main.cpp')
0 files changed, 0 insertions, 0 deletions