Skip to content

Plasma Search plugins order not respected #180

Closed

Description

@dcog989

Before you submit

  • I searched open and closed issues for this problem.
  • 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.

AppGrid version

1.9.0-rc.6

Did this work in an earlier version?

No — broken since I installed AppGrid

Last known good version

No response

Variant

Panel (Plasma popup)

Plasma version

6.6.5

Distro

CachyOS

Install method

AUR -rc (plasma6-applets-appgrid-rc)

Session

Wayland

Graphics card / driver

No response

Plasma theme

No response

Screenshots / video

Image Image Image

plasmashell log (optional)

Anything else

No response

Activity

  1. added
    enhancementNew feature or request
    and removed
    bugSomething isn't working
    on Jun 9, 2026
  2. added this to the 1.9.0 milestone on Jun 9, 2026
  3. xarbit commented on Jun 9, 2026

    @xarbit
    Owner

    Thx will look in to this, it's not implemented which is why i changed it to a feature.

  4. dcog989 commented on Jun 9, 2026

    @dcog989
    ContributorAuthor

    Thanks. My LLM says:

    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).

  5. xarbit commented on Jun 9, 2026

    @xarbit
    Owner

    Thanks. My LLM says:

    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.

  6. xarbit commented on Jun 9, 2026

    @xarbit
    Owner

    i will test this through, it will go in 1.9.0 following a new RC .

  7. xarbit commented on Jun 9, 2026

    @xarbit
    Owner

    rc 7 is out please test this.

  8. dcog989 commented on Jun 9, 2026

    @dcog989
    ContributorAuthor

    Perfect! Many thanks.

    The RC is looking very good. Nice work.

  9. dcog989 commented on Jun 9, 2026

    @dcog989
    ContributorAuthor

    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'??

  10. xarbit commented on Jun 9, 2026

    @xarbit
    Owner

    Will look in to it .. there will be differences though :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions