If there's e.g. an infinite loop during main() that would previously result in a blank page, but not error message. The expected case is that we would get a RangeError exception, but that exception never reaches the catch handlers in qtloader.js. Work around this by setting noInitialRun, followed by calling main manually. We then need to handle the case where the app.exec() workaround throws, which should not trigger an error. Pick-to: 6.7 Change-Id: Ia8431279308770981316cd168e4316341bfb2531 Reviewed-by: Morten Johan Sørvig <morten.sorvig@qt.io> |
||
|---|---|---|
| .. | ||
| a11y | ||
| clipboard | ||
| cursors | ||
| eventloop | ||
| localfiles | ||
| network | ||
| qstdweb | ||
| qtloader | ||
| qtloader_integration | ||
| qtwasmtestlib | ||
| rasterwindow | ||
| selenium/qwasmwindow | ||
| shared | ||
| CMakeLists.txt | ||
| README.md | ||
README.md
Manual tests and examples for Qt on WebAssembly
These examples demonstrates various technical aspects of the Qt for WebAssambly platform port, and can be used as a reference when writing application code.
Content
cursors Cursor handling
eventloop Event loops, application startup, dialog exec()
localfiles Local file download and upload
rasterwindow Basic GUI app, event handling
qtwasmtestlib native auto test framework