Bug 489075

Summary:	Additional Configuration Options
Product:	[Plasma] plasmashell	Reporter:	jf0918
Component:	Task Manager and Icons-Only Task Manager widgets	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	wishlist	CC:	cwo.kde, qydwhotmail
Priority:	NOR
Version First Reported In:	master
Target Milestone:	1.0
Platform:	Arch Linux
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=489131 https://bugs.kde.org/show_bug.cgi?id=489132
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description jf0918 2024-06-23 22:52:07 UTC

I would love the following options:

Activating/deactivating scrolling through the tasks loops/wraps around. If activated, scrolling past the last task activates the first one. If activated, scrolling past the first task activates the last one. If deactivated, wrapping around does not occur. 

Tasks that demand attention (highlighted in orange) show up in the task manager, even if those tasks are on a different virtual desktop. I have my tasks separated by virtual desktop (only tasks of the current virtual desktop are shown in the bar), but if a task of another virtual desktop demands attention, it shows up in EVERY task manager. An option to disable this behavior could be helpful. This option would only display that task in the task manager, if it's virtual desktop would be the active one, even if that task demanded attention.

Comment 1 cwo 2024-06-24 00:23:05 UTC

Thanks for the bug report! Unfortunately it reports multiple distinct issues, which will make it not actionable. See https://community.kde.org/Get_Involved/Issue_Reporting#Multiple_issues_in_a_single_Bugzilla_ticket for more explanation.
Can I ask you to submit a new bug report for each specific issue? Thanks again!

Also, the first request could use some explicit motivation. What usage patterns would this change allow that you cannot do now?

Comment 2 jf0918 2024-06-24 18:39:07 UTC

(In reply to cwo from comment #1)
> Thanks for the bug report! Unfortunately it reports multiple distinct
> issues, which will make it not actionable. See
> https://community.kde.org/Get_Involved/
> Issue_Reporting#Multiple_issues_in_a_single_Bugzilla_ticket for more
> explanation.
> Can I ask you to submit a new bug report for each specific issue? Thanks
> again!
> 
> Also, the first request could use some explicit motivation. What usage
> patterns would this change allow that you cannot do now?

Thanks for the feedback. I've split them up and tried to give some more context to the first issue.