f8b3c1f0a7
They match what QTimer already provides these days, and we want to minimize porting for users come Qt 7, so we don't want users to first write QChronoTimer::singleShot() (because it exists) and then back to QTimer::singleShot(); we want them to continue to use QTimer. The only reason QChronoTimer is a separate class from QTimer is that the latter has an int interval property and we can't just port it to milli- or nanoseconds chrono types if we want users to actually access the extra range or precision afforded by the chrono types. But that's not an issue for the singleShot() static methods, as they never return an object that could be asked for its timeout. (No ChangeLog needed, as QChronoTimer is new in 6.8) Found in API-review. Fixes: QTBUG-128426 Change-Id: Ief8b7c8d25380c0e9e9c5c36c90ce34c147557ae Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io> (cherry picked from commit 6e5eb082c934cb94c45f3e13b3f7c2deb2e7b2e6) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| CMakeLists.txt | ||
| tst_qchronotimer.cpp | ||