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 11131 - ConstructorElementNode not activated after opening Java file
Summary: ConstructorElementNode not activated after opening Java file
Status: CLOSED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Linux
: P4 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-04-06 12:52 UTC by Marian Petras
Modified: 2007-09-26 09:14 UTC (History)
0 users

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 Marian Petras 2001-04-06 12:52:41 UTC 
(NetBeans 3.2 beta, build 21 / RedHat Linux 6.2 / Sun JDK 1.3.0)

ConstructorElementNode of a Java class does not get activated before some
MethodElementNode was activated.

If a cursor in JavaEditor is moved to body of a constructor, the JavaNode is
activated (instead of the ConstructorElementNode). If you then move the cursor
to body of some method (thus activate its MethodElementNode) and move the cursor
back to the constructor, the ConstructorElementNode gets activated correctly.

The behaviour is then correct until the file is reopened.
Comment 1 Svata Dedic 2001-04-06 17:22:38 UTC 
Sorry, does not seem as a P3 bug for me. Unless it has severe impact on some 
other module, I would give it P-4 or less.
Comment 2 Jan Chalupa 2001-05-05 23:21:15 UTC 
Target milestone -> 3.3
Comment 3 Svata Dedic 2001-09-12 18:55:08 UTC 
Fixed in dev builds. There's still an open issue when an editor is 
opened and docked into a pre-existing frame. Since the editor does 
not gain focus, the appropriate node cannot be activated.
Comment 4 Jan Becicka 2001-11-06 16:50:00 UTC 
Verified
Comment 5 Quality Engineering 2003-07-01 13:14:37 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.