qt5base-lts

History

David Faure 4e9944e6c8 QMimeDatabase: collect glob patterns from all locations A QMimeTypePrivate used to belong to a single provider, which would provide the complete data for it. But since the redesign in commit `7a5644d648`, each provider represents is a single mime directory, and the merging happens at the QMimeDatabase level. So we need a QMimeType[Private] to be just a name (a "request" for information about this mimetype) and the information for that mimetype is retrieved on demand by querying the providers and either stopping at the first one (e.g. for icons) or merging the data from all of them (e.g. for glob patterns). The XML provider was using QMimeTypePrivate as data storage, give it its own struct QMimeTypeXMLData for that purpose instead. Task-number: QTBUG-116905 Change-Id: Ia0e0d94aa899720dc0b908f40c25317473005af4 Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>		2023-09-13 13:45:04 +02:00
..
auto	QMimeDatabase: collect glob patterns from all locations	2023-09-13 13:45:04 +02:00
baseline	Mark all of Qt as free of Q_FOREACH, except where it isn't	2023-08-19 05:19:42 +00:00
benchmarks	QCborValue: add benchmark for operator[]	2023-09-06 16:17:52 +02:00
global
libfuzzer	Change the license of all CMakeLists.txt and *.cmake files to BSD	2022-08-23 23:58:42 +02:00
manual	embeddedwindows: Mask the painting manually by applying a clip	2023-09-12 16:30:02 +02:00
shared	xcb: Implement native window helper for embeddedwindows/foreign window test	2023-09-12 02:47:24 +02:00
testserver	Use SPDX license identifiers	2022-05-16 16:37:38 +02:00
CMakeLists.txt	Rid of 'special case' markers	2023-04-13 18:30:58 +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.