qt5base-lts

History

Laszlo Agocs 2189e0f2fc rhi: Make the new direct buffer update available for non-uniform buffers The original restriction to UniformBuffer was due to the GL backend where there is no GL buffer object for QRhiBuffers with usage UniformBuffer. However, we can still implement this for cases when there is a true GL buffer object underneath. With other backends it should all work as-is already. This becomes useful when one has buffers with usage Vertex that need full updates every frame. (f.ex. instance data) Unfortunately this involves renaming the function. But while at it, add an autotest case as well. Change-Id: Iff59e4509a8bae06654cc92fe8428bd79eb012fb Reviewed-by: Andy Nichols <andy.nichols@qt.io>		2020-10-12 07:55:37 +02:00
..
auto	rhi: Make the new direct buffer update available for non-uniform buffers	2020-10-12 07:55:37 +02:00
baselineserver	Another round of replacing 0 with nullptr	2020-10-07 23:02:47 +02:00
benchmarks	Another round of replacing 0 with nullptr	2020-10-07 23:02:47 +02:00
global
libfuzzer	CMake: Regenerate projects to use new qt_internal_ API	2020-09-23 16:59:06 +02:00
manual	rhi: Make the new direct buffer update available for non-uniform buffers	2020-10-12 07:55:37 +02: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
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.