3fe0bf6e1b
The example follows bad and outdated practices: - running time consuming and I/O heavy workload in the GUI thread - calling processEvents to keep the UI responsive - showing results only at the end of a search rather than continuously Perhaps this example can be rewritten at some point to apply modern practices (at least use a thread and emit signals), but it seems to have low overall educational value. Moving it to be a manual test for now. Fixes: QTBUG-111002 Pick-to: 6.5 Change-Id: Id630fd4599096448ea4f96bcbf977b11a039796f Reviewed-by: Axel Spoerl <axel.spoerl@qt.io> Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> |
||
---|---|---|
.. | ||
animation | ||
desktop | ||
dialogs | ||
doc | ||
draganddrop | ||
effects | ||
gallery | ||
gestures | ||
graphicsview | ||
itemviews | ||
layouts | ||
mainwindows | ||
painting | ||
qnx/foreignwindows | ||
richtext | ||
scroller | ||
tools | ||
touch | ||
tutorials | ||
widgets | ||
windowcontainer | ||
CMakeLists.txt | ||
widgets.pro |