Now that I've discovered the awesomeness of KWin's scripting and effect scripting capabilities, I wrote a little effect. It animates the opacity and scale of a given window. I wanted to apply an easing curve so the animation looks more natural. The curve property has no effect, however. animate({ window: window, duration: zoominEffect.duration, curve: QEasingCurve.InOutQuad, animations: [{ type: Effect.Opacity, from: 0.0, to: 1.0 }, { type: Effect.Scale, curve: QEasingCurve.InOutQUad, from: 0.75, to: 1.0 }] }); Did I overlook something? Are not all properties of QEasingCurve exported to JS? Is it not possible on the global animate level? Reproducible: Always
- curve: QEasingCurve.InOutQuad, + curve: 3, At least the stock scripted effects use integers. No idea whether the enum is accessible from QtScript
> At least the stock scripted effects use integers. No idea whether the enum is accessible from QtScript it should be, at least I think I exported the bits, will check
Tried it with curve: 3, didn't help
yeah QEasingCurve is exported: m_engine->globalObject().setProperty("QEasingCurve", m_engine->newQMetaObject(&QEasingCurve::staticMetaObject))
Hod did you perceive it doesn't work? Tried to raise animationTime and with a curve that is more aggressive (InOutExpo) or excentric (InOutElastic)?
Exactly :-) Raised the animation time to 4 seconds and tried with both curve: 31 and curve: QEasingCurve.InOutElastic no effect
Please attach the complete script for inspection.
Created attachment 77484 [details] main.js of effect
Wild shot: Try placing the curve only inside the animation settings /only/ ie animate({ window: window, duration: loginEffect.duration, animations: [{ type: Effect.Opacity, from: 1.0, to: 0.0, curve: QEasingCurve.InOutQuad }, { type: Effect.Scale, from: 1.0, to: 1.5, curve: QEasingCurve.InOutQuad }] }); Reasonable test later ;-)
That worked. :)
We should test whether commit b7eb49ad0966a5a2164a775c8c72d59346bcfd30 fixed this.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!