Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
No one has replied
@p3c0 Thanks for your help, I will try your option, I hope I could use QQuickWidget instead of QQmlApplicationEngine with no problem or unexpected effect.
@sierdzio : Thanks. I got a similar comment at my SO crosspost. I've posted there what I could gather from the docs.
@maximo Ok :) I think to get it to repaint itself is easy for Quick experts but if this works for you, then its ok, i guess.
@zepfan As told earlier the rendering is all done by OpenGL which in turn is handled by the GPU so that wont matter. The Timer is what is affecting the CPU. QtQuick renderer is capable of handling thousands of items at a time. Please check it here. Also here are some benchmark examples. Extremetable example loads 100000 items as and when required. Anyway here are some more link that you may fine useful: http://doc.qt.io/qt-5/qtquick-performance.html http://www.sletta.org/apps/blog/show/42708211-looking-at-throughput-in-qt-quick http://doc.qt.io/qt-5/qtquick-visualcanvas-scenegraph-renderer.html Try profiling your example.