wasm: streamline the exec warning

State the problem and suggest possible solutions for the
app developer.

Pick-to: 6.4
Change-Id: I0484c4eb31020ec0016005f43f910f32a319b850
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
This commit is contained in:
Morten Sørvig 2022-08-10 13:31:41 +02:00
parent f347682fd5
commit 83cf2985e9

View File

@ -369,12 +369,8 @@ void QEventDispatcherWasm::handleApplicationExec()
void QEventDispatcherWasm::handleDialogExec()
{
if (!qt_have_asyncify()) {
qWarning() << "Warning: dialog exec() is not supported on Qt for WebAssembly in this"
<< "configuration. Please use show() instead, or enable experimental support"
<< "for asyncify.\n"
<< "When using exec() (without asyncify) the dialog will show, the user can interact"
<< "exec() call never returns, stack content at the time of the exec() call"
<< "is leaked, and the exec() call may interfere with input event processing";
qWarning() << "Warning: exec() is not supported on Qt for WebAssembly in this configuration. Please build"
<< "with asyncify support, or use an asynchronous API like QDialog::open()";
emscripten_sleep(1); // This call never returns
}
// For the asyncify case we do nothing here and wait for events in wait()