1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
|
/****************************************************************************
**
** Copyright (C) 2016 The Qt Company Ltd.
** Contact: https://www.qt.io/licensing/
**
** This file is part of the test suite of the Qt Toolkit.
**
** $QT_BEGIN_LICENSE:GPL-EXCEPT$
** Commercial License Usage
** Licensees holding valid commercial Qt licenses may use this file in
** accordance with the commercial license agreement provided with the
** Software or, alternatively, in accordance with the terms contained in
** a written agreement between you and The Qt Company. For licensing terms
** and conditions see https://www.qt.io/terms-conditions. For further
** information use the contact form at https://www.qt.io/contact-us.
**
** GNU General Public License Usage
** Alternatively, this file may be used under the terms of the GNU
** General Public License version 3 as published by the Free Software
** Foundation with exceptions as appearing in the file LICENSE.GPL3-EXCEPT
** included in the packaging of this file. Please review the following
** information to ensure the GNU General Public License requirements will
** be met: https://www.gnu.org/licenses/gpl-3.0.html.
**
** $QT_END_LICENSE$
**
****************************************************************************/
import QtQuick 2.15
/*
QTBUG-92984.
Have three Image (with semi-transparency) and two semi-transparent
Rectangle elements, and so all in the alpha render list, with images that
are big enough to not get atlased. (meaning the underlying nodes never get
merged, but the nodes for the Rectangle elements might)
Lay them out vertically below each other, with the two Rectangles on top of
the second and third Images, respectively. Then change (swap) the source
property of the Images. This triggers a rebuild in the batch renderer.
Verify that the results are still correct, i.e. that the two Rectangle
elements do not get merged. An incorrect result would be having the third
Image rendered on top of the corresponding Rectangle due the two Rectangles
(incorrectly) being in one merged batch. The Image should always be below,
regardless of which nodes get changed, invalidated, and how batches get
rebuilt.
The base-final sample set 1 just verifies that the Image changes from the
blueish to greenish. The important part is the second set of samples: this
checks that the red(ish) rectangle is still on top of the third Image. With
incorrect merging behavior the second final result would be the same as the
first final one (i.e. the "background" Image rendered, incorrectly, on top
of the Rectangle).
#samples: 4
PixelPos R G B Error-tolerance
#base: 30 115 0.24313 0.30588 0.99607 0.05
#base: 30 124 0.847059 0.062745 0.2 0.05
#final: 30 115 0.36078 0.99607 0.42745 0.05
#final: 30 124 0.870588 0.2 0.0862745 0.05
*/
RenderTestBase {
id: root
property string selectedItem: "item2"
Item {
width: 150; height: 50
Image {
width: parent.width
objectName: "item1"
source: "widebtn1.png"
}
}
Item {
y: 50; width: 150; height: 50
Image {
width: parent.width
objectName: "item2"
source: selectedItem == objectName ? "widebtn2.png" : "widebtn1.png"
}
Rectangle {
anchors.fill: parent
anchors.margins: 20
color: "red"
opacity: 0.8
}
}
Item {
y: 100; width: 150; height: 50
Image {
id: img3
width: parent.width
objectName: "item3"
source: selectedItem == objectName ? "widebtn2.png" : "widebtn1.png"
}
Rectangle {
width: parent.width + 50
anchors.centerIn: parent
height: img3.height - 40
color: "red"
opacity: 0.8
}
}
onEnterFinalStage: {
selectedItem = "item3";
finalStageComplete = true;
}
}
|
