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 35106

Summary:	L&F: Loop of NPEs while painting Java node properties.
Product:	platform	Reporter:	Jiri Kovalsky <jkovalsky>
Component:	Explorer	Assignee:	_ tboudreau <tboudreau>
Status:	VERIFIED INVALID
Severity:	blocker	CC:	mmirilovic
Priority:	P3	Keywords:	L&F
Version:	3.x
Hardware:	PC
OS:	Windows ME/2000
Issue Type:	DEFECT	Exception Reporter:
Attachments:	L&F library put into <ide_dir>/lib directory. NullPointerException thrown if Java node is clicked.

Description Jiri Kovalsky 2003-07-23 15:07:57 UTC

Development build #200307230100 of NetBeans 4.0
Windows 2000 with JDK 1.4.1_02 build #06
-ui com.jgoodies.plaf.plastic.PlasticXPLookAndFeel

Description:
============
Selecting some Java data node in the Explorer
results in never ending loop of
NullPointerExceptions if above mentioned look and
feel is used. IDE is unusable in such situation
because no property can be changed.

Comment 1 Jiri Kovalsky 2003-07-23 15:09:07 UTC

Created attachment 11096 [details]
L&F library put into <ide_dir>/lib directory.

Comment 2 Jiri Kovalsky 2003-07-23 15:10:10 UTC

Created attachment 11097 [details]
NullPointerException thrown if Java node is clicked.

Comment 3 Jiri Kovalsky 2003-07-23 15:18:29 UTC

This is Look and Feel specific issue.

Comment 4 _ tboudreau 2003-07-28 13:27:47 UTC

This is a bug in Plastic L&F.

It is probably assuming the button has a parent when it is
painted.  In the case of the problem button, it does not - 
for efficiency, it is simply configured and painted in the
right place on screen.

Generally it should be possible to paint a component which
has no parent - I suggest firing a bug report at Karsten.

A workaround is possible (there is unoptimized painting 
logic for JComboBoxes due to a similar problem), but better
to fix the look and feel.  This is one danger when writing a
look and feel - making unwarranted assumptions about the
state of a component.

Comment 5 Jiri Kovalsky 2003-07-28 13:45:00 UTC

Okay, I won't force you to implement the workaround. I hope they will
fix it. Verified as invalid bug.