Bug 162469 - give access to all items in KMenu
Summary: give access to all items in KMenu
Status: RESOLVED INTENTIONAL
Alias: None
Product: kmenuedit
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-22 15:21 UTC by Maciej Pilichowski
Modified: 2009-11-24 20:56 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2008-05-22 15:21:40 UTC
Version:            (using KDE 3.5.9)

Such entries like switch user or switch session are hardcoded. Please give access to them, so the user could move them,copy them, etc.
Comment 1 Will Stephenson 2009-11-23 18:46:10 UTC
They are not .desktop files. This would be a massive PITA to support and would require a rewrite of the menus. I'm sure there are plasma wishlists requesting this ability, join one of those, eg 202795.
Comment 2 Maciej Pilichowski 2009-11-24 17:04:24 UTC
I don't see here big issue -- there are other parts which are not .desktop files as well (favourites, latest, etc.) and they can be hidden/shown. It is only a flag -- "show in the menu" (or hide from...). While displaying the menu the entries are filtered -- no danger here.

Please reconsider and reopen this report -- excluding mentioned entries is really helpful for not experienced users.
Comment 3 Will Stephenson 2009-11-24 17:25:11 UTC
There's no way for KMenuEdit to easily get at these non-desktop-file items, since they are added to the tree of desktop-file items by the application launchers as they build the menu widgets to show, and are not configurable in a common way.  So this wishlist would require a rewrite of the app launchers to do everything via .desktop files or some other common mechanism.
Comment 4 Maciej Pilichowski 2009-11-24 20:56:41 UTC
Ok, maybe it is not JJ :-) but do the possible problems justify a wontfix? After all, maybe somebody will be interested in doing this, wontfix will filter out this report.