Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
QSR 1.2
-
None
-
82c1e251d495d5122190c7f121d9b75c8314dbff
Description
Valid code:
states: [
State { name: "A"; PropertyChanges {target: kuva2; x: 40; y: 10; opacity: 1.0; width: 10; height: 10}},
State { name: "B"; PropertyChanges {target: kuva2; x: 60; y: 10; opacity: 1.0; width: 20; height: 30}},
State { name: "C"; PropertyChanges {target: kuva2; x: 80; y: 10; opacity: 1.0; width: 40; height: 50}},
State { name: "D"; PropertyChanges {target: kuva2; x: 100; y: 10; opacity: 1.0; width: 60; height: 60}},
State { name: "E"; PropertyChanges {target: kuva2; x: 120; y: 10; opacity: 1.0; width: 80; height: 90}},
State { name: "F"; PropertyChanges {target: kuva2; x: 140; y: 10; opacity: 1.0; width: 150; height: 150}},
State { name: "G"; PropertyChanges {target: kuva2; x: 160; y: 10; opacity: 1.0; width: 200; height: 200}}
]
malfunctioning code with whitespace after the target name before the ;
states: [
State { name: "A"; PropertyChanges {target: kuva2 ; x: 40; y: 10; opacity: 1.0; width: 10; height: 10}},
State { name: "B"; PropertyChanges {target: kuva2 ; x: 60; y: 10; opacity: 1.0; width: 250; height: 250}},
State { name: "C"; PropertyChanges {target: kuva2 ; x: 80; y: 10; opacity: 1.0; width: 10; height: 10}},
State { name: "D"; PropertyChanges {target: kuva2 ; x: 100; y: 10; opacity: 1.0; width: 10; height: 10}},
State { name: "E"; PropertyChanges {target: kuva2 ; x: 120; y: 10; opacity: 1.0; width: 10; height: 10}},
State { name: "F"; PropertyChanges {target: kuva2 ; x: 140; y: 10; opacity: 1.0; width: 10; height: 10}},
State { name: "G"; PropertyChanges {target: kuva2 ; x: 160; y: 10; opacity: 1.0; width: 10; height: 10}}
]
The first one generates bitmaps correctly.
The second code does not generate bitmaps at all.
Both code samples were tested with qmlscene tool, and it accepts the whitespace after the target name. So the problem is in the QSR tooling and animation validation.