This avoids fading the image source, or the fill mode, or the source size on startup while we're still setting things up.
While a Timer is usually a bad idea, this simplifies the code a lot.
Details
- Reviewers
- None
- Group Reviewers
Plasma - Commits
- R120:87ec46be03b4: [Image Wallpaper] Just use Timer to determin when we're ready
Trust me, I've been trying to come up with a solution for it needlessly fading things on startup for weeks. Either this or we'll leave it broken..
- Started plasmashell, image wallpaper was there instantly rather than having it fade in.
- Changing image or fill mode or resizing plasmoidviewer still animates nicely
- Slideshow image still transitions
Diff Detail
- Repository
- R120 Plasma Workspace
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Meh. If there's nothing by 5.12.0 push it, but hopefully we can get something better by then.
At a glance, I'd assume it's failing because onFillModelChanged and onModelChanged are both called during startup resulting in the second one doing a fade?
wallpapers/image/imagepackage/contents/ui/main.qml | ||
---|---|---|
109 | why are you removing this check? |
Hello!
This commit causes a regression on my system. [1] In summary, during plasma's start-up the desktop background/wallpaper is initially displayed, but as soon as kscreen sets up the displays there are a number of flickers and the wallpaper is replaced with black background. I can reproduce this issue relatively reliably with compositing switched off.
I was able to resolve this issue locally by reverting this commit on my system, and I verified that the reverted commit resolves the aforementioned regression. I found this commit by inspecting the git history.
Would it be possible to revert and/or rework this commit?
Thank you!
[1] An x86_64 laptop with an up-to-date version of Kubuntu 18.04 with plasma-workspace 5.12.7, connected to an external display using HDMI.