This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 48778 - entries in Keyboard Shortcuts dialog have the same name
Summary: entries in Keyboard Shortcuts dialog have the same name
Status: CLOSED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Projects UI (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P4 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords: UI
Depends on:
Blocks: 41535
  Show dependency tree
 
Reported: 2004-09-09 14:52 UTC by Patrick Keegan
Modified: 2006-03-24 10:17 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Keegan 2004-09-09 14:52:32 UTC 
In the keyboard shortcuts dialog, the action name
for selecting the Projects window ("Projects") is
the same as the action name for selecting the
current file's node in the Projects window. Rename
the later to something like "Select Node in Projects"

The same goes for Files
Comment 1 Jiri Rechtacek 2004-09-14 17:14:00 UTC 
Checking in src/org/netbeans/modules/project/ui/actions/Bundle.properties;
/cvs/projects/projectui/src/org/netbeans/modules/project/ui/actions/Bundle.properties,v
 <--  Bundle.properties
new revision: 1.17; previous revision: 1.16
done
Comment 2 Patrick Keegan 2004-09-15 12:13:15 UTC 
verified in continuous build 20040915-0845
Comment 3 Petr Hrebejk 2004-09-20 17:14:03 UTC 
This was probably not the right way how to fix it. Please see iddue
#49175. Please rollback this fix. You need to implement the
popupresenter in the SelectNodeAction to fix it correctly.
Comment 4 Petr Hrebejk 2004-09-20 17:27:11 UTC 
But you don't have to do it. Just make this issue duplicate of issue
#46051. :-)
Comment 5 Jesse Glick 2004-09-20 17:40:47 UTC 
Well the bug as reported here was fixed, regardless of what other
problems it may have caused.
Comment 6 Petr Hrebejk 2004-09-20 17:48:57 UTC 
Hmm I think this should rather be solved generaly in the
LookupSensitiveAction other actions extending it have the same
problem. This is why I suggested roll back of the changes to making
this dupe of #46051.
Comment 7 Marian Mirilovic 2005-12-20 15:46:02 UTC 
This issue was solved long time ago. Because nobody has reopened it neither
added comments, we are verifying/closing it now. 
If you are still able to reproduce the problem, please reopen. Thanks in advance.