https://bugs.kde.org/show_bug.cgi?id=432999
--- Comment #20 from Arjen Hiemstra <[email protected]> --- Git commit 801772616953ab7017722489de0c342ac9c1ed75 by Arjen Hiemstra. Committed on 11/11/2022 at 18:13. Pushed by ahiemstra into branch 'master'. declarative/core: Use two opacity nodes for fading in IconItem There's no need to create a complete custom node with material and shaders if all we're doing is a linear fade between the old image and the new. Instead we can use two QSGOpacityNodes for the fading, which gives us the same effect without the need for so much custom code. Moreover, at least one of the duplicates of 432999 points to problems in fadingnode, so this hopefully reduces the changes of that occuring. M +0 -6 src/declarativeimports/core/CMakeLists.txt D +0 -12 src/declarativeimports/core/fadingmaterial.frag D +0 -8 src/declarativeimports/core/fadingmaterial.vert D +0 -14 src/declarativeimports/core/fadingmaterial_core.frag D +0 -9 src/declarativeimports/core/fadingmaterial_core.vert D +0 -238 src/declarativeimports/core/fadingnode.cpp D +0 -38 src/declarativeimports/core/fadingnode_p.h M +63 -38 src/declarativeimports/core/iconitem.cpp M +3 -0 src/declarativeimports/core/iconitem.h D +0 -8 src/declarativeimports/core/shaders.qrc D +0 -14 src/declarativeimports/core/shaders6/CMakeLists.txt D +0 -21 src/declarativeimports/core/shaders6/fadingmaterial.frag D +0 -18 src/declarativeimports/core/shaders6/fadingmaterial.vert https://invent.kde.org/frameworks/plasma-framework/commit/801772616953ab7017722489de0c342ac9c1ed75 -- You are receiving this mail because: You are watching all bug changes.
