Bug 55586 - Cannot undo removed items
Summary: Cannot undo removed items
Status: ASSIGNED
Alias: None
Product: kmenuedit
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
: 112612 163542 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-03-06 01:02 UTC by Brian "netdragon" Bober
Modified: 2008-06-08 18:19 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Brian "netdragon" Bober 2003-03-06 01:02:13 UTC 
Version:            (using KDE KDE 3.0.5)
Installed from:    RedHat RPMs
OS:          Linux

When you remove an item from the menu, you cannot undo it. I deleted it accidentally because I clicked on the wrong spot. I really meant to click "New Item" instead of "Delete". I wasn't prompted and therefore lost the menu items. <offtopic> Please also prompt for confirmation. I would file that as a bug if it didn't exist, but I don't like this wizard and enter_bug.cgi doesn't work properly </offtopic>
Comment 1 Stephan Binner 2003-03-06 20:51:53 UTC 
Please update to KDE 3.1, afair this was fixed.
Comment 2 Waldo Bastian 2004-05-12 16:53:50 UTC 
In KDE 3.2 an explicit "Save" action is required.

TODO: Add proper undo functionality.
Comment 3 Carsten Lohrke 2007-05-17 13:24:54 UTC 
Since KDE switched to XDG style xml menu, the functionality to restore deleted menu entiries is dead. The only way is to edit the file manually. This causes confusion for end users and "invalid" bug reports on distributors side. Would you like me to open a new bug for this or do we reuse this one changing it from "wish" to "major" or so!?
Comment 4 Pino Toscano 2007-11-04 14:26:17 UTC 
*** Bug 112612 has been marked as a duplicate of this bug. ***
Comment 5 Pino Toscano 2008-06-08 18:19:54 UTC 
*** Bug 163542 has been marked as a duplicate of this bug. ***