qt5base-lts

History

Alexander Volkov 0c28e1ab7a Fix finding the closest active touch point for the pressed touch point Currently pressed touch point is added to the list of active touch points in Gui module. It must be excluded from consideration when we traverse the list. Task-number: QTBUG-43255 Change-Id: Idddab093b1f6a79122cf18fad7f43bfc93ce7eea Reviewed-by: Shawn Rutledge <shawn.rutledge@digia.com> Reviewed-by: Marc Mutz <marc.mutz@kdab.com>		2015-04-16 15:22:36 +00:00
..
auto	Fix finding the closest active touch point for the pressed touch point	2015-04-16 15:22:36 +00:00
baselineserver	Update license headers and add new license files	2014-09-24 12:26:19 +02:00
benchmarks	Benchmarks: Build gui benchmarks only when gui module available	2015-01-16 08:14:49 +01:00
global	tst_bic: Add linux-gcc-ia32 bic data for QtXml	2013-01-16 08:25:28 +01:00
manual	SSL NPN negotiation: Do not abort on unmatched protocols	2015-02-05 14:07:19 +00:00
shared	Update license headers and add new license files	2014-09-24 12:26:19 +02:00
README	Doc: Fix references to Qt Test	2013-01-30 01:35:06 +01:00
tests.pro	iOS: Enable building of basic tests	2014-01-22 12:35:17 +01: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.