Details
-
Task
-
Resolution: Done
-
P3: Somewhat important
-
5.6.0
-
None
-
81867dfbf9c16d4300727a08eed9b5c6c979e0ba
Description
ShaderEffect is a relatively heavy compnent to construct compared to other built in components like Image and Rectangle. This isn't an issue when using ShaderEffect for large, infrequent effects, but can become an issue when e.g. using it on every element in a GridView.
Some ideas:
- See if lookThroughShaderCode can be applied per-unique-shader, rather than per-ShaderEffect-instance.
- String-based connects; QSignalMapper; string-based property lookups, etc are all relatively heavy weight. See if they can be replaced by lighter weight alternatives.
Attachments
Issue Links
- relates to
-
QTBUG-52496 QML ShaderEffect unnecessarily slow?
- Closed
-
QTBUG-84377 Port shader effect property connection optimization to QQuickGenericShaderEffect
- Closed
For Gerrit Dashboard: QTBUG-53901 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
163340,8 | QtQuick: clean up shader effect property connections | dev | qt/qtdeclarative | Status: MERGED | +2 | 0 |