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 37159 - Filesystems node has bad popup menu
Summary: Filesystems node has bad popup menu
Status: VERIFIED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC All
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-12 10:16 UTC by ehucka
Modified: 2007-09-26 09:14 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 ehucka 2003-11-12 10:16:04 UTC 
NB build 200311111900

Steps to reproduce:

1. open a project and mount a filesystem with java
files
2. invoke popup menu for example on a Fields node
of some java class - popup contains Add Field.. action
3. switch to another project - main menu
Project|Project Manager
4. try to invoke popup on the Filesystem node
5. it will be invoked the same popup menu as on
Fields before

Workaround: Select some other node in filesystem.
Comment 1 Vitezslav Stejskal 2003-11-12 12:34:16 UTC 
This doesn't sound like a projects problem.
Comment 2 pzajac 2003-11-12 13:11:50 UTC 
I think, that this is a problem of project. Who is responsible for
selecting first node in filesystem explore after project switch?
Comment 3 Jan Pokorsky 2004-01-19 14:07:26 UTC 
Projects has no influence on that. Probably bug in explorer/actions?
Comment 4 Jiri Rechtacek 2004-01-27 10:30:36 UTC 
Responsibility of java module. DefaultFactory$ElementCategoryNode
doesn't notify that node is destroyed (e.g. FieldElementNode does),
same defect has been also in nb35.
Emanuel, I decrease the priority to P3 because appears only for
Fileds, Methods, Constructors, ... nodes. If I'm wrong, increase
again. Thanks
Comment 5 Jan Pokorsky 2004-03-03 18:18:46 UTC 
Please clarify who and how DefaultFactory$ElementCategoryNode should
notify that node (which???) is destroyed.

From steps mentioned above I understand that no node is being deleted
but the explorer is updating its content. So how can the java module
help here?
Comment 6 Martin Matula 2004-07-17 11:33:26 UTC 
The old projects has been replaced. The issue does not seem to be
relevant anymore.
Comment 7 ehucka 2004-08-17 16:42:46 UTC 
verified
Comment 8 Quality Engineering 2007-09-20 09:54:23 UTC 
Reorganization of java component