ea1a6d3ae0
We do have an implicit constructor which allows construction of a QLocale from the QLocale::Language enum values. It will be used when doing the comparison. However, do not rely on the implicit conversions, and provide the operators that explicitly do the right thing. This also allows us to save an extra allocation of QLocalePrivate. Found in Qt 6.8 API review. Amends 71bbc35a3774ba7411970ff74068f5211b73e425. As a drive-by: fix the order of the test slots in the unit test. Change-Id: I37f8f5881469b7734705e06e471746814dd2ddf0 Reviewed-by: Edward Welbourne <edward.welbourne@qt.io> Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> (cherry picked from commit 403b1abcad5f437c51dfabd7095b814e99e197a1) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
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.