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 83206 - need a context menu to "edit" properties for a launcher
need a context menu to "edit" properties for a launcher
Status: RESOLVED DUPLICATE of bug 72715
Product: nautilus
Classification: Core
Component: Desktop
1.1.x
Other Linux
: Normal enhancement
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-05-28 00:11 UTC by Damien Covey
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Damien Covey 2002-05-28 00:11:30 UTC
Need to be able to edit the "launcher properties" for a desktop item. 
Currenly can only edit the file properties for a desktop item.  For
example, if I create a new launcher, but neglect to add a comment or
generic name, I cannot go back and chage these.  I have to delete the
launcher, and then make it again.  Can get annoying if you keep forgeting
something.  Also makes it hard to change the defult icons on the destop.
Comment 1 Gregory Merchan 2002-05-28 01:16:45 UTC
I concur that it should be possible to edit launchers, but adding
a menu item would be suboptimal. The existing file properties panel
should support doing this.
Comment 2 Dave Bordoley [Not Reading Bug Mail] 2002-05-28 03:53:29 UTC
basically this bug is a dupe of the menu editing bug for
adding/editing menu launchers, so i'm marking it a dupe of it. Just to
let you guys know, there is some disagreement over what is the best
way to do this for 2.0. Alexl has stated in the past that he would
like this to be integrated into the existing nautilus properties
dialog, and this is definately the longterm solution. Short term may
see us using the panel edit dialog (which sucks, but may be the only
viable 2.0.0 solution).

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