After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 150507 - "Remove this item" - should confirm (desktop files in the menu)
"Remove this item" - should confirm (desktop files in the menu)
Status: RESOLVED DUPLICATE of bug 137953
Product: gnome-panel
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-08-19 02:33 UTC by Sridhar Ratna
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sridhar Ratna 2004-08-19 02:33:06 UTC
Description of Problem:
When removing an entry form GNOME-Menu a
confirmation dialog should be displayed

Steps to reproduce the problem:
1. Right-click on main menu entry 
2. Select 'Remove this Item'
3. 

Actual Results:
Item is removed without mercy

Expected Results:
Action must be performed after confirmitating from
the user

How often does this happen? 
Everythim

Additional Information:
Debian-Sarge/gnome-2.6.2
Comment 1 Vincent Untz 2004-08-19 07:10:52 UTC
See bug #95007. You can lock applets, so you won't remove them accidentally. Is
there any other reason you'd want a confirmation dialog?
Comment 2 Sridhar Ratna 2004-08-19 14:40:14 UTC
You _can_ lock applets.  But you cannot lock the menu items (in Applications
menu).  So it's better to show confirmation dialog atleast for the Applications
menu items.

PS: After locking, you can't remove 'Applications' menu applet, but you can
remove the items in it with a single click - no confirmation!
Comment 3 Vincent Untz 2004-08-19 14:56:42 UTC
Ah, I had not understood this was about the desktop files in the menu.
Comment 4 Vincent Untz 2004-12-22 09:30:43 UTC
I'm marking this as a duplicate of bug #137953, where we're talking about our
future menu editor.

*** This bug has been marked as a duplicate of 137953 ***