qt6-bb10

History

Allan Sandfeld Jensen 967e55a628 Allow creating a valid QColorSpace one value at a time The change to using setters left a quirk from the previous un-mutable design where you couldn't set values on an invalid color space and create a valid one. This changes that so it works as expected for an imperative API, but is also needed for the declarative QML bindings. Change-Id: I246cfc38b364b156238151c42c1df82a3f1cc9d3 Reviewed-by: Eirik Aavitsland <eirik.aavitsland@qt.io>		2020-02-01 00:31:01 +01:00
..
auto	Allow creating a valid QColorSpace one value at a time	2020-02-01 00:31:01 +01:00
baselineserver	QAbstractSocket: deprecate 'error' member-function	2020-01-10 12:54:53 +01:00
benchmarks	Deprecate all methods that use QMatrix	2020-01-28 04:12:25 +01:00
global	…
libfuzzer	Fuzzing: Move fuzz target to match path of tested code	2020-01-07 21:15:09 +01:00
manual	Manual test foreignwindows: Modernize code	2020-01-28 22:39:07 +01:00
shared	Remove usages of Q_OS_WINCE	2019-05-23 13:51:05 +02:00
testserver	docker-compose now brings up the docker images tagged as "latest"	2019-12-05 15:40:00 +01:00
README	…
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.