qt5base-lts

History

Andy Shaw c057e23b02 When creating QVariant(QPolygonF()) this should be a null variant The handling of the null QPolygonF case was not correct as it would always be seen as valid. This ensures it is treated in the same way as QPolygon when it is in fact null. [ChangeLog][QtGui][QPolygonF] When a QVariant holds a QPolygonF() then it will be correctly seen as a null QVariant. Change-Id: Icae34f513c3a8e1dd3f50cb64a3d13ae7c636cc4 Reviewed-by: Stephen Kelly <stephen.kelly@kdab.com> Reviewed-by: Jędrzej Nowacki <jedrzej.nowacki@digia.com>		2013-10-18 20:05:09 +02:00
..
auto	When creating QVariant(QPolygonF()) this should be a null variant	2013-10-18 20:05:09 +02:00
baselineserver	Add QT_NO_PROCESS guards in tests where they are missing	2013-09-03 08:42:24 +02:00
benchmarks	Allow non-character codes in utf8 strings	2013-10-17 09:50:58 +02:00
global
manual	Add widget replace function to QLayout	2013-09-21 23:17:55 +02:00
shared
README	Doc: Fix references to Qt Test	2013-01-30 01:35:06 +01:00
tests.pro

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.