Linked by Thom Holwerda on Tue 20th Dec 2011 22:01 UTC, submitted by RichterKuato
Thread beginning with comment 501065
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
So, unless Qt 5 has vastly improved rendering performance over Qt 4, what will happen when developers will start to put pretty animated transitions everywhere in their software, as is somewhat encouraged by the QML part of the Qt SDK ?
Animated transitions are not the problem, they execute well in 2D.
Shader effect programs are prone to be problematic, and probably shouldn't be used without real hw acceleration. Luckily you can avoid using them - QML doesn't force you to add everything in your UI, even if it makes it straightforward (provided that you know how to write gl shader programs, of course).




Member since:
2010-03-08
Including when tapping into Qt's new animation capabilities ?
I know that the QML demos of Qt 4.7 are somewhat sluggish on the Fedora 15 install of my laptop, which offers a typical example of imperfect GPU support (Dual-GPU setup in which the Intel chip works reasonably well and the NVidia chip doesn't).
My problem with that is that as outdated as pre-Sandy Bridge Intel GPUs may be, I believe they still vastly outperform Mesa OpenGL emulation on CPUs for the same period. If you know of a simple way to temporarily disable GPU acceleration on Linux, I can experimentally test this belief.
So, unless Qt 5 has vastly improved rendering performance over Qt 4, what will happen when developers will start to put pretty animated transitions everywhere in their software, as is somewhat encouraged by the QML part of the Qt SDK ?