qt5base-lts

History

Fabian Kosmale 331a200b97 Revert "QObject: simplify part of connection logic" This reverts commit `1918c689d7`. The template gets always instantiated in QObjectPrivate::connect, even if the connection types is not Qt::(Blocking)QueuedConnection. For non-queued connections we however support using incomplete types in connect. The only way to fix this would be to make the connection type a template parameter of QObjectPrivate::connect (or at lesat pass some compile time constant indicating "blocking"-ness) along, so that we can use if constexpr instead of if. As all involved classes are private, we can postpone investigating this solution to 6.1 Change-Id: Ieffaf015f8e60ca6ac6f85eb9e2756e480060b4f Reviewed-by: Lars Knoll <lars.knoll@qt.io>		2020-10-27 16:43:12 +01:00
..
auto	Revert "QObject: simplify part of connection logic"	2020-10-27 16:43:12 +01:00
baselineserver	Another round of replacing 0 with nullptr	2020-10-07 23:02:47 +02:00
benchmarks	Add constructor benchmarks for QLocale, to test likely sub-tag matching	2020-10-26 15:56:06 +02:00
global	tst_bic: Add linux-gcc-ia32 bic data for QtXml	2013-01-16 08:25:28 +01:00
libfuzzer	CMake: Regenerate projects to use new qt_internal_ API	2020-09-23 16:59:06 +02:00
manual	Expunge WA_GroupLeader	2020-10-27 02:55:59 +01:00
shared	Replace Q_DECL_UNUSED with [[maybe_unused]]	2020-10-03 11:58:08 +02:00
testserver	Fix perl script warning	2020-03-19 14:15:04 +00:00
.prev_CMakeLists.txt	Make standalone tests build via top level repo project	2019-11-08 15:42:32 +00:00
CMakeLists.txt	CMake: Refactor optimization flag handling and add optimize_full	2020-10-06 10:07:05 +02:00
README	Doc: Fix references to Qt Test	2013-01-30 01:35:06 +01:00
tests.pro	Build examples and tests only if their requirements are met	2017-03-22 15:55:55 +00:00

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.