26e3a06aca
Basically this should work exactly the same as constructing the QUtcTimeZonePrivate directly. Follow-up performance optimizations should not change any of this behavior. Pick-to: 6.5 5.15 Change-Id: I2a3e78965f3a553b8b70cb12f7772b9fdfbf7bf7 Reviewed-by: Marc Mutz <marc.mutz@qt.io> (cherry picked from commit 7a79ce13a93aab724e8943d83fc903c88466d053) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> (cherry picked from commit 9cba61e5eb7cbbfb197f2b90d33b294e43291065) |
||
|---|---|---|
| .. | ||
| auto | ||
| baseline | ||
| benchmarks | ||
| global | ||
| libfuzzer | ||
| manual | ||
| shared | ||
| testserver | ||
| CMakeLists.txt | ||
| README | ||
README
This directory contains autotests and benchmarks based on Qt Test. In order
to run the autotests reliably, you need to configure a desktop to match the
test environment that these tests are written for.
Linux X11:
* The user must be logged in to an active desktop; you can't run the
autotests without a valid DISPLAY that allows X11 connections.
* The tests are run against a KDE3 or KDE4 desktop.
* Window manager uses "click to focus", and not "focus follows mouse". Many
tests move the mouse cursor around and expect this to not affect focus
and activation.
* Disable "click to activate", i.e., when a window is opened, the window
manager should automatically activate it (give it input focus) and not
wait for the user to click the window.