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 8773 - Top-node isn't displayed in Component Inspector
Summary: Top-node isn't displayed in Component Inspector
Status: CLOSED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P4 normal (vote)
Assignee: David Strupl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-12-05 17:02 UTC by Marian Mirilovic
Modified: 2008-12-23 11:16 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Error ide log file (5.14 KB, text/plain)
2000-12-05 17:02 UTC, Marian Mirilovic 		Details
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 Mirilovic 2000-12-05 17:02:09 UTC 
[boston](1160)
only Solaris

You must open some Frame , for example :
- open  Development -> examples -> texteditor -> all files ( About, Finder, Ted)
- close all Form editors
- close source editor
- open About, open Finder
now you don't see top node(name of class) in component inspector ( first line in
CI is free), this name you may see if you go Down - bottom last component , name
will displayed upper last line
if you don't see and you double click left mouse button on this place , you
caught exception ArrayIndexOutOfBoundsException
Comment 1 Marian Mirilovic 2000-12-05 17:02:59 UTC 
Created attachment 372 [details]
Error ide log file
Comment 2 Tomas Pavek 2001-02-02 14:46:59 UTC 
This looks like a bug in Swing - some inconsistency between JTree and its
model, I'd guess (according to the exception and the fact the tree is totally
disordered). Similar problems are reproducible in main explorer and were seen
also in other places (javacvs - selecting classpath mounting point). Happened
also on Linux and Windows... but in all cases very rarely :(.
I'm wondering if we can do something with this - find some workaround in
TreeView, maybe track the problem, or just close the bug (WONTFIX).
Comment 3 Marian Mirilovic 2001-09-05 10:40:50 UTC 
In dev build I wasn't see this problem, never.

This issue seems FIXED or something else in [nb_dev](20010905). David?
Comment 4 David Strupl 2001-09-05 11:09:00 UTC 
If it does not occur in latest builds --- I am resolving it as
wontfix. It can be something in nodes hierarchy but the code has been
changed since this report and if we are not able to reproduce it I
assume this is ok. If anyone disaggree please reopen with situation in
which this happened in latest builds.
Comment 5 Marian Mirilovic 2001-09-05 11:13:38 UTC 
verified in [nb_dev](20010905)
Comment 6 Quality Engineering 2003-07-01 16:12:14 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.