https://bugs.kde.org/show_bug.cgi?id=482892

--- Comment #8 from Ivan Čukić <ivan.cu...@kde.org> ---
Seems like my comment went to ether. Trying to remember what I wrote:

> Having to deleting the plugin after every update would become really 
> annoying, really fast.

Plasma 6 disabled checking for whether a plugin should be enabled (and VD one
was disabled by default) since 76a786d2a4d8f93df2330f1c47c8cc45cd0e961f and now
all the plugins are loaded.

> Was it more an issue of the way to UI was done that was confusing?

The UI was the same as in KRunner. I agree a few checkboxes instead of them
being showed as plugins would have been better, but I don't think the UI was
confusing. And it served a purpose.


Looks like there will be some larger changes to activities:
https://invent.kde.org/plasma/kactivitymanagerd/-/merge_requests/69#note_975471

I used to have a similar setup as you. But, due to some ideas various people
had a few years ago for radically changing activities or even removing them, I
switched to a future-proof workflow that can work even with window managers
that don't support activities explicitly (for the case if KWin removes
activities, or if the tiling scripts for KWin stop working).

I've moved the applications that semantically belong to all activities
(Kontact, chat applications, music player etc.) to a dedicated activity, let's
call it Common. Alt+Tab serves as a switch between this Common activity and the
proper 'current' activity. And other shortcuts are there to activate another
proper activity. You should give it a go, I don't miss the old setup.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to