994bfd41b2
Updating the transform marks it as dirty and causes rebatching.
Since we were doing this even when nothing had changed, we were
essentially rebatching every time there was any update to the
shape. We should leave it to the node to decide if it has
been updated.
This adds two tests that verify that rebatching still happens
when changing the color/gradient of the shape.
Change-Id: Iefb7a21a89ac2c31053e473cf689fa06e34a40d5
Reviewed-by: Eirik Aavitsland <eirik.aavitsland@qt.io>
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| auto | ||
| baseline | ||
| benchmarks | ||
| global | ||
| libfuzzer/qml | ||
| manual | ||
| system | ||
| testapplications | ||
| CMakeLists.txt | ||
| README | ||
README
This directory contains autotests and benchmarks based on QTestlib. 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.