On Fri, Feb 3, 2012 at 5:24 PM, Harri Pasanen <ha...@mpaja.com> wrote:
> On 02/03/2012 08:12 PM, Adriano Rezende wrote:
>
> On Tue, Jan 24, 2012 at 9:21 AM, Harri Pasanen <ha...@mpaja.com> wrote:
> What could be happening is some kind of pixel adjustment during the
> animation. The x,y,width,height values are real numbers that are rounded to
> an int when mapping to the display, so 1-pixel shifts could happen due that
> fact.
>
> It's much more than 1-pixel, like tens of pixels. In some cases it
> looks like they are serialized.
> But it is not consistent, happens only maybe 1/10 times. Looks like some
> display list order
> is arbitrary.
>
It doesn't seem to be related to ParallelAnimation. A small test case would
highlight what is really happening.
>
> Piece {
> id: piece
> ...
>
> states: State {
> name: "moved";
> PropertyChanges { target: piece; x: nX; y: nY; restoreEntryValues:
> false }
> }
> }
>
> The if in javascript if I have Piece A and B and do
>
> A.state = 'moved'
> B.state = 'moved'
>
> sometimes B moves before A.
>
>
This "moved" state is error prone; you should never define a state that
modifies x,y of the 'root' item, since this item could be anchored from
outside leading to binding conflicts like the following:
Item {
YourPiece {
state: "moved"
anchors.fill: parent
}
}
Br,
Adriano
_______________________________________________
Qt-qml mailing list
Qt-qml@qt.nokia.com
http://lists.qt.nokia.com/mailman/listinfo/qt-qml
