Keith, thank you for your suggestion. At least I've missed this feature in several places: "The value of the QML property will be updated after the animation has finished. The property is not updated while the animation is running."
Alas, it did not solve my issue. Honestly speaking, I did not believe it may help, because with animations I had the following rendering table (obtained after parsing qmlscene's output with QSG_RENDER_TIMING=1 set): $ grep 'rendered' ubuntu12.02_5.4.log | egrep -o '[0-9]+ms' | sort -n | uniq -c 7 0ms 2 1ms 1 4ms 1 5ms 2 7ms 1 8ms 1 9ms 3 10ms 2 11ms 3 12ms 7 13ms 15 14ms 131 15ms 791 16ms 218 17ms 43 18ms 12 19ms 4 20ms 4 21ms 1 23ms 1 24ms 1 27ms 1 29ms 4 33ms 2 38ms 1 45ms So, most of the frames are rendered within 16 ms time frame provided. I am getting more inclined to the idea that it is not Qt-related issue. Something with my system, drivers, etc. On Tue, Jan 13, 2015 at 8:21 PM, Keith Gardner <kreios4...@gmail.com> wrote: > Can something further be done to avoid flickering? >> >> If you are just translating the item by changing the X value, try using > the XAnimator (http://doc.qt.io/qt-5/qml-qtquick-xanimator.html). It > performs the movement on the render thread instead of the gui thread. I > have experienced big performance gains when using the animators over the > animations. >
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
