| Summary: | Most used quick settings are pointless when set by frequency, they should be 'last used' to facilitate repeat access | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Robert Griffiths <r.griff444> |
| Component: | Quick Settings | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | wishlist | CC: | kde, nate, tneo |
| Priority: | NOR | Keywords: | usability |
| Version First Reported In: | master | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Robert Griffiths
2021-12-07 21:24:10 UTC
If we added all KCMs then it would just be a list of everything, which is not useful because that's already present on the sidebar. Am I misunderstanding, and you are requesting that this list of 5 KCMs be sorted by *recency* of use rather than *frequency* of use? Can you clarify the request? Sure, if it were me, I would simply change the 5 most used to the 5 last used. Not perfect but much better. But maybe a few more than 5? So it could be most useful when setting up for the 1st time. I use about 9 I think. I'm not sure when most used is at all useful? Users don't return to 'difficult to find' options as much as themes so the harder to find options will fall from the bottom of the list: eg if I go to printers a few times coz I forgot my password or 'something' it will move up the list, I will never need it again, and something useful will disappear! Ideally it would be user choice, with buttons to choose a few settings so as to display a 'MY settings panel'. But that is a lot of work so I propose: 'Last used' in place of 'most used', and maybe a few more than 5. I was just about to file a bug that shows entries double in the "Most used" section. Changing that to "Last used" would work for me as well. Can you make sure you show items only once? >Can you make sure you show items only once?
That's an independent bug that would be unaffected by this change either way.
If we changed this we'd get as many bug reports saying to change it back. It might be better for this use-case of changing one thing, then realising it wasn't right and changing it again, but you break the longer term case of "I have a printer, I go into printer settings often" vs not. |