Jul 7 2020
Jul 4 2020
Redesign PlasmaShell in order to have DesktopViews for each running Activity in each screen. In Example 1 that would mean six different DesktopViews that could be used afterwards as Previews in kwin scripts, desktop components etc... Personally I can not take over such big task.
Another reason I chose solution A is because it's quite natural for me to think that the activities were designed to have their own desktops, plasmoids included. But I didn't know about the tough experience that Plasma 4 had.
Jul 3 2020
As the WallpapersModel works with image/video paths and you mentioned the lack of widgets layers, I assumed that LiveDesktopPreviews would reload these resources in memory, which would be unwanted, especially when it comes to videos; don't you think so?
Jun 24 2020
This seems like it would be very useful to alleviate the issues I ran into while trying to implement T10495.
Apr 24 2020
A model like this could be quite useful I think.
I an trying to investigate if there is consensus in the community about the need of a WallpapersModel.
Mar 3 2020
Sep 8 2019
Sep 1 2019
Aug 26 2019
Next, do you think you could clean up the applications list so there aren't all those duplicates and they all get icons?
Aug 22 2019
Ping.
Aug 17 2019
Nov 29 2016
May 4 2016
p.p.s. The 'smart' termination was an attempt to fix the 'Qt SQL has no idea how to properly deinitialize on termination bug' :)
Sorry, I missed this one.
Apr 5 2016
Jan 28 2016
Nov 14 2015
FYI you could have also solved it by creating a QDBusMessage::createMethodCall
Yeah, QDBusInterface blocks as it needs introspection to generate the properties/slots and stuff. It's a confusingly rubbish class.