https://bugs.kde.org/show_bug.cgi?id=381000
--- Comment #153 from Vova Mshanetskiy <[email protected]> --- Created attachment 108739 --> https://bugs.kde.org/attachment.cgi?id=108739&action=edit Output of 108642 with QSG_INFO=1 on affected system I also tried running with QSG_VISUALIZE=changes. What is interesting, is that after i double click the window and the animation finishes, Qt's own visualization shows no more changes, while KWin's highlight-redraws effect shows constant redraws. Also, the visualization looks a bit different when running the original attachment 108642 and a modified version with OpacityAnimators replaced with NumberAnimations. With OpacityAnimatiors the last change (when the animation finishes) is highlighted with a solid color, but with NumberAnimations the last change is highlighted in a striped pattern. According to docs this means different things. Now, a bit of my background. I am a C++ developer currently working on a Qt/QML mobile app. It is my first time experience with QtQuick, but i am not new to Qt. I have tried to use Animators in several places in my project, and they never worked for me. Sometimes they just do not work, sometimes they leave the whole animated part of UI blank (while i am able to interact with it), sometimes they work or they don't depending on how i order them inside a ParallelAnimation, sometimes it depends on the value of duration property. It looks like QtQuick does not like something about hardware of my work PC, but that also happens on my Android phone. And then i have this bug. For me it looks like Animators are just buggy right now. I think i will stay away from them for a few releases of Qt. -- You are receiving this mail because: You are watching all bug changes.
