Summary: | When searching for keyboard layouts, exact matches may not be the first item in the list on the left | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | John <ilikefoss> |
Component: | kcm_keyboard | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | bharadwaj.raju777, butirsky, duha.bugs, evgeniyharchenko.dev, natalie_clarius, nate |
Priority: | NOR | Keywords: | usability |
Version: | 6.3.0 | ||
Target Milestone: | --- | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/plasma/plasma-desktop/-/commit/bd50c79c4813b19aa8cbe2cf706de849430151f6 | Version Fixed In: | 6.4.0 |
Sentry Crash Report: | |||
Attachments: | Search results for Romanian language |
Description
John
2025-02-14 10:41:15 UTC
From a technical perspective, this is correct since the lists are both ordered alphabetically. However I see how it's not ideal in this specific use case. Perhaps we could prioritize exact matches in the left column. I agree that it's correct by search on both columns, but for my use case and usability in general I think that the language should be prioritized as the user searches for the languages mainly. Then of course, if there are more variants / countries) maybe it wants to choose that, if the default is not the right one. Honestly I'm not even sure why the right column is searched at all. I can't think of a language right now that can be found on the right column and not on the left. One other thing that could be done after the language is matched on the left column, would be to order the variants by country size in population to have more chances of suggesting the right one for the user. Like: English - > United States (first in the right column) German -> Germany (first in the right column) French -> France (first...) Italian -> Italy (first...) Romanian -> (Romanian standard, instead of Romanian, here as that's the one that most of us use and it has the right diacritics, but I think this needs a bug report with a bit more documentation on my side). It would be a bit weird for Spanish as Spain not being the first, but at least it will be the suggestion that most people wanted. But anyway, that would probably take a lot of time to implement. So, I at least, would be happy with prioritizing the left column. A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/2840 Git commit bd50c79c4813b19aa8cbe2cf706de849430151f6 by Nate Graham, on behalf of Bharadwaj Raju. Committed on 03/03/2025 at 21:38. Pushed by ngraham into branch 'master'. kcms/keyboard: implement fuzzy search for layouts Implements scored fuzzy search for layouts using KFuzzyMatcher. FIXED-IN: 6.4.0 M +1 -0 kcms/keyboard/CMakeLists.txt M +5 -5 kcms/keyboard/layoutmodel.h A +70 -0 kcms/keyboard/layoutsearchmodel.cpp [License: GPL(v2.0+)] A +38 -0 kcms/keyboard/layoutsearchmodel.h [License: GPL(v2.0+)] M +2 -0 kcms/keyboard/qml/plugin.cpp M +30 -27 kcms/keyboard/ui/LayoutDialog.qml https://invent.kde.org/plasma/plasma-desktop/-/commit/bd50c79c4813b19aa8cbe2cf706de849430151f6 |