| Summary: | Option to focus unfocused, un-grouped task on scroll | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | irchaika |
| Component: | Task Manager and Icons-Only Task Manager widgets | Assignee: | Eike Hein <hein> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | CC: | gabor, nate, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.19.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | patch to change the behavior | ||
|
Description
irchaika
2020-09-29 16:52:48 UTC
*** Bug 429525 has been marked as a duplicate of this bug. *** Where is the relevant code for this? I downloaded plasma-desktop's code, and checked icontasks, also checked tasksmanager but couldn't find something directly related. Probably applets/taskmanager/package/contents/ui/code/tools.js in the plasma-desktop repo, but I'm not 100% sure. Created attachment 137444 [details] patch to change the behavior (In reply to Nate Graham from comment #3) > Probably applets/taskmanager/package/contents/ui/code/tools.js in the > plasma-desktop repo, but I'm not 100% sure. It indeed was, I had a lot of trouble navigating the code, here's a pretty bad hack that works for what I wanted. This should be taken into account: -If you scroll on empty space that belongs to the applet, or on a pinned but unopened program, it will still scroll to the next-previous program (I'd rather it did nothing in those scenarios, but can't really be bothered). -I think said scrolling might have been reverted compared to how it would normally work. If someone else wants to do something t hat isn't a complete hack, take into account that: -"anchor" represents the program we're scrolling over. -tasksModel.requestActivate(target) is what actually sets the focus. -and target is an element of the array taskIndexList. I couldn't find a better way to find the position of anchor in TaskIndexList so I used "pushCounter". Now that you've got a preliminary patch, I would recommend submitting it! It's okay if it's not perfect, but it's much easier to do code review on GitLab than here in the bug report. :) Here's the documentation: https://community.kde.org/Infrastructure/GitLab Make sure to add BUG 427122 to the commit message on its own line. |