Bug 484169

Summary: "Keep launchers separate" should work with sorting modes other than manual
Product: [Plasma] plasmashell Reporter: Ivan Topolsky <doktor.yak>
Component: Task Manager and Icons-Only Task Manager widgetsAssignee: Plasma Bugs List <plasma-bugs-null>
Status: CONFIRMED ---    
Severity: wishlist CC: kdedev, nate, qydwhotmail
Priority: NOR    
Version First Reported In: 6.0.2   
Target Milestone: 1.0   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Ivan Topolsky 2024-03-21 15:04:44 UTC
SUMMARY

"Keep launchers separate" is grayed out even in "Sort" modes where it is relevant (e.g.: in "By desktop").

Context: I want the "Pin" to only be visible if the corresponding app is not running. If it is running, I only want the Classic Task Manager's button, not the "pin".

See: https://mstdn.science/@dryak/112133815180180834


STEPS TO REPRODUCE
1. Right click -> "Configure Task manager"
2. "Behaviour" pane
3. Section "Sort:"

OBSERVED RESULT

My "Sort" is on the default "By desktop".
"Keep launchers separate" is grayed out, so I cannot un-check it to obtain the behaviour desired (see "context" above).

EXPECTED RESULT

4. Un-check "Keep launchers separate" checkbox.
5. "Ok"
6. Now "pins" are hidden if the app is running and there's a Task button

WORKAROUND

4. Switch "Sort:" to "Manual" (this un-grays the checkbox)
5. Un-check "Keep launchers separate" checkbox.
6. Switch back to your favourite "Sort" - e.g. "By desktop" (this re-grays the checkbox, but now it's un-checked).
7. "Ok"
8. Now "pins" are hidden if the app is running and there's a Task button


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
Opensuse Tumbleeed 20240319
KDE Plasma Version: 
6.0.2
KDE Frameworks Version: 
6.0.2
Qt Version: 
6.6.2

ADDITIONAL INFORMATION
"minor" as this is just a UX/UI hiccup (need to fight around gray out check box)
the actual desired functionnality (hiding "pins" automatically) works.
Comment 1 TraceyC 2024-09-24 19:10:50 UTC
I can confirm the reported behavior in git-master
Comment 2 Nate Graham 2025-10-23 19:00:51 UTC
It's actually intentional, not a bug. It could be changed, of course.