Bug 497155

Summary: Allow for per-activity customization of desktop effects
Product: [Plasma] kwin Reporter: George Raptis <george-raptis>
Component: activitiesAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED INTENTIONAL    
Severity: wishlist CC: kde, nate
Priority: NOR Keywords: usability
Version: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description George Raptis 2024-12-07 12:26:33 UTC 
CONTEXT

I use my computer for many reasons ranging from listening to music to creating circuits. To be more efficient, I use different virtual desktop for when doing different things. But, when, for example, I need to be productive, I want to use less desktop effects so my work is efficient, but when I want to use my computer for other tasks I like having more effects, for cosmetic purposes. 

Therefore, I propose the addition of the ability to customize the desktop effect not only to a global extend (like the case is now), but for each virtual desktop individually as well.
 
Generally, this suggestion could also serve as a starting point for giving more meaningful functionality to virtual desktop by allowing to have custom configuration on various aspects (effects, shortcuts, wallpaper, icons, widgets etc.), rather than having a homogeneous design without the ability to individualize them for different purposes.

Linux/KDE Plasma: Fedora Linux 41 KDE Plasma
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0 
Qt Version: 6.8.0
Comment 1 Nate Graham 2024-12-11 22:41:33 UTC 
In general this is the use case that Activities is envisioned for, not Virtual Desktops. Virtual Desktops are purely about getting more space for windows.

Even if we make this about per-activity customization of effects, I very much doubt it will be implemented as it's too specific. But we'll see.
Comment 2 David Edmundson 2025-01-02 16:42:23 UTC 
We're not doing this at a KDE level. It's not just the implementation but also presenting settings to the user in a way that's vaguely comprehensible.

What does exist is a hook to run user scripts when an activity changes. 

You can run  qdbus org.kde.KWin /Effects org.kde.kwin.Effects.unloadEffect  loadEffect respectively.