qt5base-lts

History

Eskil Abrahamsen Blomfeldt e0ad2cee55 Fix querying font aliases that share name with other fonts `a332f3fabc` disabled resolving all fonts on the system for every font lookup, which was a significant startup time improvement. But it also caused a regression: When a font has an alias which shares the name of a proper font, then this would not be resolved correctly. This is fairly typical on Windows/GDI due to backwards-compatibility. Instead of being collected under a shared typographical family, fonts are disambiguated by adding the style name to the family name. The proper typographical name is still available, but this is not enumerated by the system. So "Segoe UI" for instance, will be available as "Segoe UI", "Segoe UI Light", "Segoe UI Bold" etc. When we populate family aliases, we register that "Segoe UI Light" is actually "Segoe UI" with Light weight, and prior to `a332f3fabc` this would be done implicitly. But after the optimization, we would only populate family aliases once we stumbled over a font request for a non-existent font. For "Segoe UI", we would simply return the regular weight font as the best imperfect match. The fix is to populate font family aliases not only when the family is non-existent, but when the match is imperfect, e.g. if we are asking for a Light weight font and only finding a regular one. User code can still avoid this somewhat expensive operation by using the full family names on Windows. This also requires a fix to a test. When removeApplicationFont() is called, we invalidate the font database, so it will be reset to a state that does not contain the family aliases. Therefore we cannot guarantee that it is identical to what it was before the test started, since this depends on what has happened previously in the application. [ChangeLog][QtGui][Text] Fixed an issue where some font styles and weights would not be selectable. This was especially noticeable on Windows. Pick-to: 5.15 6.1 6.2 Fixes: QTBUG-94835 Change-Id: I892855edd1c8e3d3734aace396f6000d897d2ec4 Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io> Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>		2021-09-11 11:59:51 +00:00
..
auto	Fix querying font aliases that share name with other fonts	2021-09-11 11:59:51 +00:00
baselineserver	Another round of replacing 0 with nullptr	2020-10-07 23:02:47 +02:00
benchmarks	Deprecate constructing QString from a pointer	2021-09-07 18:53:37 +08:00
global
libfuzzer	Fuzzing: Discard more logging output from QSslCertificate	2021-08-30 22:05:49 +02:00
manual	xcb: add manual test for xrandr scale	2021-09-02 21:57:02 +02:00
shared	Include what you use ! filesystem.h uses QOperatingSystemVersion	2021-08-27 20:31:18 +02:00
testserver	Network self-test: make it work with docker/containers	2020-11-17 19:56:06 +01:00
CMakeLists.txt	CMake: Refactor optimization flag handling and add optimize_full	2020-10-06 10:07:05 +02:00
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.