Bug 489075 - Additional Configuration Options
Summary: Additional Configuration Options
Status: RESOLVED NOT A BUG
Alias: None
Product: plasmashell
Classification: Plasma
Component: Task Manager and Icons-Only Task Manager widgets (show other bugs)
Version: master
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-23 22:52 UTC by jf0918
Modified: 2024-06-24 18:39 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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.