Details
-
Bug
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
QSR 1.2
-
None
Description
In the spirit of the requirement 2.3.4.5
2.3.4.5 Animations with safe elements must be generated and validated at build time.
Given the following QML example
SafeText {
id: mytext0
objectName: "mytext0"
color: "#000000"
font.bold: false
font.italic: false
font.pixelSize: 12
height: 20
x: 0
y: 0
opacity: 0.0
width: 15
runtimeEditable: true
text: "1"
states: [
State { name: "1"; PropertyChanges {target: mytext0; x: 0; y: 139; opacity: 0.0; color:"#0000ff"}},
State { name: "2"; PropertyChanges {target: mytext0; x: 0; y: 279; opacity: 1.0; color:"#00ff00"}},
State { name: "3"; PropertyChanges {target: mytext0; x: 0; y: 419; opacity: 0.0; color:"#ff0000"}},
State { name: "4"; PropertyChanges {target: mytext0; x: 0; y: 559; opacity: 1.0; color:"#ffff00"}},
State { name: "5"; PropertyChanges {target: mytext0; x: 0; y: 699; opacity: 0.0; color:"#ff00ff"}},
State { name: "6"; PropertyChanges {target: mytext0; x: 0; y: 839; opacity: 1.0; color:"#00ffff"}},
State { name: "7"; PropertyChanges {target: mytext0; x: 0; y: 979; opacity: 0.0; color:"#ffffff"}}
]
transitions: [
Transition {
from: "*"
to: "*"
NumberAnimation {
properties: "x, y, opacity, color"
duration: 1000
easing.type: Easing.InOutQuad
easing.type: Easing.InOutQuad
}
}
]
}
The Qt Creator in edit mode complaints about this for the latter duplicate row easing.type: Easing.InOutQuad
And if checking with the qmlscene tool, the output is:
D:\QtQSR1.2\X_RC3_tests\TC_R2.3.4.9.1_Host_Win_10\indicators_R23491>d:\QtQSR1.2\5.15.2\mingw81_64\bin\qmlscene.exe file2.ui.qml
file:///D:/QtQSR1.2/X_RC3_tests/TC_R2.3.4.9.1_Host_Win_10/indicators_R23491/file2.ui.qml:68 Property value set multiple times
But the QSR tooling is ignorant for this kind of thing. Obviously a educated user would spot this issue if done due to a mistake, if he/she/it would:
- Use Qt Creator when processing the QML code, OR
- validate the QML with the qmlscene tool
But the question is, should the QSR tooling react to this? And to any similar kind of possible errors?
