From b1f1fc42c1b93d2ebbb14f1524845beae4e8c572 Mon Sep 17 00:00:00 2001 From: Lorn Potter Date: Wed, 21 Sep 2022 19:42:16 +1000 Subject: wasm: add asyncify use cases Change-Id: Ic937f3f4f1d8c5266c4da89d9ec1cc89713c2268 Reviewed-by: Paul Wicking (cherry picked from commit e5a44a670666fa611d51b149fe09e6d525b55dc1) Reviewed-by: Qt Cherry-pick Bot --- doc/src/platforms/wasm.qdoc | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/doc/src/platforms/wasm.qdoc b/doc/src/platforms/wasm.qdoc index 2adb2d17..cf886c68 100644 --- a/doc/src/platforms/wasm.qdoc +++ b/doc/src/platforms/wasm.qdoc @@ -525,6 +525,13 @@ these restrictions by allowing synchronous calls (like QEventLoop::exec() and QD to yield to the event loop. Nested calls are not supported, and for this reason asyncify is not used for the top-level QApplication::exec() call. +Features that require asyncify are: +\list + \li QDialogs, QMessageBoxes with return values. + \li Drag and drop (specifically drag). + \li Nested/secondary event loops exec(). +\endlist + As of Qt 6.4, Asyncify support is enabled in the binary package, but needs to be enabled for applications by adding -sASYNCIFY -Os to linker options: -- cgit v1.2.1