On 21/09/2010, at 8:43 PM, ext
[email protected]<mailto:[email protected]> wrote:
The following assignment to ‘value’ does not work. Only the final Rotation in
the list seems to get assigned to the target property. Known issue? Or doing
something silly?!
Binding {
target: albumImage
property: "transform"
value: [
Rotation {
axis.x: 1; axis.y: 0; axis.z: 0
angle: 180
origin.y: picColumn.picSize*1.32
},
Scale {
xScale: picColumn.sizeFactor; yScale: picColumn.sizeFactor;
origin.x: picColumn.picSize/2; origin.y: picColumn.picSize
},
Translate {
x: -picColumn.width/2 + picColumn.deltaX
y: -coverflow.height*0.1 -picColumn.place*picColumn.place*20
},
Rotation {
angle: picColumn.rotateY
origin.x: picColumn.picSize/2; origin.y: picColumn.picSize/2
axis.x: 0; axis.y: 1; axis.z: 0
}
]
when: picColumn.visible
}
Hi Simon,
It looks like the engine is incorrectly interpreting the assignment of the list
of transforms to "value" as 4 individual object assignments (each effectively
overriding the previous). I've created
http://bugreports.qt.nokia.com/browse/QTBUG-13798 for this issue.
Regards,
Michael
_______________________________________________
Qt-qml mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-qml