You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm on the latest stable AppGrid release (or current main).
What happened?
I search for 'index' and the results show browser history first, Settings last - the opposite of how those plugins are arranged. Same for 'btop' - browser history before apps.
Note: KDE Application Launcher behaves as expected.
Reproduction steps
See screenshots.
Expected behaviour
The app should display results in order of plugin arrangement.
Why Kicker (KDE Application Launcher) gets it right but AppGrid doesn't:
Kicker shows each KRunner plugin type in its own section — "Applications", "System Settings", "Bookmarks", etc. — each sorted by relevance within that section. So cross-plugin ordering is moot.
AppGrid lumps all non-app KRunner results into one flat "Search Plugins" section. KRunner::ResultsModel sorts by CategoryRelevance (Highest=100 → Lowest=0), then by Relevance (0-1 float). But if every runner plugin sets the same CategoryRelevance (e.g., Moderate), the sort degenerates to match relevance alone — a bookmark with 0.95 relevance can appear above a system setting with 0.5, which looks wrong.
So the root cause is: ResultsModel's internal sort cannot meaningfully differentiate runner types in a flat list without separate category relevance levels per runner. AppGrid needs its own runner-type priority to override this when flattening all runners into one section.
The fix is still to add lessThan() to RunnerFilterModel, sorting by runner plugin ID priority (services → systemsettings → calculator → bookmarks/webshortcuts → others).
Why Kicker (KDE Application Launcher) gets it right but AppGrid doesn't:
Kicker shows each KRunner plugin type in its own section — "Applications", "System Settings", "Bookmarks", etc. — each sorted by relevance within that section. So cross-plugin ordering is moot.
AppGrid lumps all non-app KRunner results into one flat "Search Plugins" section. KRunner::ResultsModel sorts by CategoryRelevance (Highest=100 → Lowest=0), then by Relevance (0-1 float). But if every runner plugin sets the same CategoryRelevance (e.g., Moderate), the sort degenerates to match relevance alone — a bookmark with 0.95 relevance can appear above a system setting with 0.5, which looks wrong.
So the root cause is: ResultsModel's internal sort cannot meaningfully differentiate runner types in a flat list without separate category relevance levels per runner. AppGrid needs its own runner-type priority to override this when flattening all runners into one section.
The fix is still to add lessThan() to RunnerFilterModel, sorting by runner plugin ID priority (services → systemsettings → calculator → bookmarks/webshortcuts → others).
The cause was a one-line omission: AppGrid created the ResultsModel but never fed it the user's arrangement.
Just noticed a minor difference to the KDE Launcher - they display a separator above each search plugin with its name, e.g. Browser History_____________ - that would be nice to offer as part of 'Show divider lines'??
Activity
xarbit commentedon Jun 9, 2026
Thx will look in to this, it's not implemented which is why i changed it to a feature.
dcog989 commentedon Jun 9, 2026
Thanks. My LLM says:
xarbit commentedon Jun 9, 2026
The cause was a one-line omission: AppGrid created the ResultsModel but never fed it the user's arrangement.
xarbit commentedon Jun 9, 2026
i will test this through, it will go in 1.9.0 following a new RC .
fix(search): respect KRunner plugin arrangement in results (#180)
xarbit commentedon Jun 9, 2026
rc 7 is out please test this.
fix(search): respect KRunner plugin arrangement in results (xarbit#180)
dcog989 commentedon Jun 9, 2026
Perfect! Many thanks.
The RC is looking very good. Nice work.
dcog989 commentedon Jun 9, 2026
Just noticed a minor difference to the KDE Launcher - they display a separator above each search plugin with its name, e.g.
Browser History_____________- that would be nice to offer as part of 'Show divider lines'??xarbit commentedon Jun 9, 2026
Will look in to it .. there will be differences though :)