qt5base-lts

History

Shawn Rutledge 1fdbbb49d9 Calculate velocity in QMutEventPoint::setTimestamp() with Kalman filter This functionality was only in Qt Quick in Qt 5. Now we move it up to QtGui so that every QEventPoint will have a valid velocity() before being delivered anywhere. [ChangeLog][QtGui][QPointerEvent] Every QEventPoint should now carry a valid velocity(): if the operating system doesn't provide it, Qt will calculate it, using a simple Kalman filter to provide a weighted average over time. Fixes: QTBUG-33891 Change-Id: I40352f717f0ad6edd87cf71ef55e955a591eeea1 Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>		2020-09-16 14:47:36 +02:00
..
auto	Calculate velocity in QMutEventPoint::setTimestamp() with Kalman filter	2020-09-16 14:47:36 +02:00
baselineserver	Use QList instead of QVector in benchmarks tests	2020-06-25 10:13:31 +02:00
benchmarks	QStyleOptionGraphicsItem: remove deprecated member matrix/levelOfDetail	2020-09-06 18:31:43 +02:00
global	tst_bic: Add linux-gcc-ia32 bic data for QtXml	2013-01-16 08:25:28 +01:00
libfuzzer	Add ; to Q_UNUSED	2020-07-07 11:51:48 +02:00
manual	Switch QSurfaceFormat::colorSpace to a QColorSpace	2020-09-15 01:41:13 +02:00
shared	Use C++17 [[maybe_unused]]	2020-09-06 18:31:43 +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: Properly handle CONFIG += thread aka Threads::Threads	2020-08-06 19:15:39 +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.