Bug 184392

Summary: Enable an easy way to List Application names in the KDE Classic Menu in Alphabetical Order
Product: [Plasma] plasma4 Reporter: Eugene Markow <ejmarkow>
Component: widget-kickoffAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED FIXED    
Severity: wishlist CC: jjesse, lmenut, mail
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: applications are not sorted correctly in "classic menu" (simplelauncher)
fixes sorting of applications in simplelauncher

Description Eugene Markow 2009-02-15 13:46:30 UTC
Version:            (using KDE 4.2.0)
Compiler:          gcc 4.3.3-1 
OS:                Linux
Installed from:    Unspecified Linux

Linux Distribution: Arch Linux
DE: KDE 4.2
Kernel: Linux Kernel Version 2.6.28.3

In KDE 4.2, when using the 'classic menu', I notice that most application names listed are not in alphabetical order, and there is no way to enable this in either ascending or descending order. Can an easy way to enable applications listed in alphabetical order be implemented?
Comment 1 Luc Menut 2009-02-22 18:37:00 UTC
Created attachment 31548 [details]
applications are not sorted correctly in "classic menu" (simplelauncher)
Comment 2 Luc Menut 2009-02-22 18:40:30 UTC
In "classic menu" (simplelauncher), applications are always sorted by generic name, even if applications are displayed by "Name Description" (the default), "Name Only" or "Name - Description". So applications are not displayed correctly in alphabetical order in these cases.

The patch in attachment fixes this; applications are sorted by application name when applications are displayed by "name", "name description" or "name - description", and by generic name when applications are displayed by "description" or "description (name)".

regards,
Luc
Comment 3 Luc Menut 2009-02-22 18:43:56 UTC
Created attachment 31549 [details]
fixes sorting of applications in simplelauncher
Comment 4 Sebastian Sauer 2009-02-22 23:08:04 UTC
Fix committed with r930245 in trunk and r930246 in the 4.2-branch. Thanks for 
the patch :)
Comment 5 Nicolas L. 2009-03-06 03:33:51 UTC
*** Bug 177331 has been marked as a duplicate of this bug. ***