| Summary: | Feature Request: Option for Meta + Number key behavior. | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | SaNNa <alx.pav2106> |
| Component: | Task Manager and Icons-Only Task Manager widgets | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | wishlist | CC: | nate, qydwhotmail |
| Priority: | NOR | ||
| Version First Reported In: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
SaNNa
2025-10-07 18:30:15 UTC
Can you describe why none of the existing options are sufficient to achieve the workflow or UX you prefer? Because when in the behaviour settings, in "Clicking grouped tasks" I select "Show small window previews" it displays them, but clicking the number again just removes the previews, it doesn't peek at them (In reply to SaNNa from comment #2) > Because when in the behaviour settings, in "Clicking grouped tasks" I select > "Show small window previews" it displays them, but clicking the number again > just removes the previews, it doesn't peek at them If I'm missing an update just let me know, I'm using plasmashell 6.3.6 but I'm now updating to the latest available When you say "peek at them", do you mean that each press of the Meta+Number key should actually cycle to the next window in the group? I mean I press Meta + number, and then to switch between windows I keep on holding Meta and press number for each window I want to go through. P.S. By peek I mean display window's contents without giving the actual focus, or if it's too hard to code, I'd also be happy with giving a focus to a window and then taking that focus back if the user had decided to cycle through it. (In reply to SaNNa from comment #5) > I mean I press Meta + number, and then to switch between windows I keep on > holding Meta and press number for each window I want to go through. > P.S. By peek I mean display window's contents without giving the actual > focus, or if it's too hard to code, I'd also be happy with giving a focus to > a window and then taking that focus back if the user had decided to cycle > through it. And then when I release Meta the current window that I selected is supposed to be given focus to. And if the user had selected a window (released Meta) that already has focus, the window should be defocused (In reply to SaNNa from comment #7) > And if the user had selected a window (released Meta) that already has > focus, the window should be defocused I mean not defocused but minimized Thanks. I don't think we'll be doing this, sorry, There are already a lot of window switching options and it's not clear to me how this would be any better than what we already have. If I'll do that myself, will somebody approve my pull request? It depends on how much code it adds, the quality of the code, whether the new option is able to be comprehensibly communicated to the user, and whether the final result presents a UX that's better than anything we have right now, either in general, or for any specific use cases. It never hurts to try I suppose! |