11d6932560
The density of Q_FOREACH uses in this and some other modules is still extremely high, too high for anyone to tackle in a short amount of time. Even if they're not concentrated in just a few TUs, we need to make progress on a global QT_NO_FOREACH default, so grab the nettle and stick to our strategy: Mark the whole of Qt with QT_NO_FOREACH, to prevent new uses from creeping in, and whitelist the affected TUs by #undef'ing QT_NO_FOREACH locally, at the top of each file. For TUs that are part of a larger executable, this requires these files to be compiled separately, so add them to NO_PCH_SOURCES (which implies NO_UNITY_BUILD_SOURCES, too). In tst_qglobal.cpp and tst_qcollections.cpp change the comment on the #undef QT_NO_FOREACH to indicate that these actually test the macro. Task-number: QTBUG-115839 Change-Id: Iecc444eb7d43d7e4d037f6e155abe0e14a00a5d6 Reviewed-by: Edward Welbourne <edward.welbourne@qt.io> |
||
|---|---|---|
| .. | ||
| a11y | ||
| clipboard | ||
| cursors | ||
| eventloop | ||
| localfiles | ||
| network | ||
| qstdweb | ||
| qtloader | ||
| qtloader_integration | ||
| qtwasmtestlib | ||
| rasterwindow | ||
| selenium/qwasmwindow | ||
| shared | ||
| CMakeLists.txt | ||
| 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