Name: krT82822 Date: 11/22/99


11/3/99 eval1127@eng -- the previous report referred to was 93531. I have just searched all of my email folders, and a test case was not actually ever received.

Java(TM) 2 Runtime Environment, Standard Edition (build1.3beta-O)
Java(TM) HotSpot Client VM (build1.3beta-O-release, 1.3beta-O-release,
intrepreted mode)
I have a JTree with a custom renderer. When setting JTree.setEnabled(false),
the tree correctly becomes disabled, but the custom rendered is replaced with
the standard renderer. This had worked nicely in Java 1.2, where it simply
greyed-out my custom icons.

I have also submitted this as a Swing 1.1.1 bug on 1999-08-05. <name withheld>
(Sun), sent an email the same day, acknowleging that some changes had
been made that may have "broken" this function and requesting a sample
application for testing. I sent him a Jar'ed application that same day, but have
not heard from him or received a bug# since then.

Now I've tried the Java 1.3beta, and I find the bug is still there, so I am
submitting another report under the Java1.3beta category. I still have the
sample application (just shows a JTree with custom renderers and a button to
toggle the enabled status). It is a jar file since it contains a couple classes
and some custom icons. I can email it to anyone upon request (13kb).

This bug really makes the application looks confusing when my clients use the
GUI and the tree suddenly looks totally different just because they selected a
GUI option that disables the tree. I can't upgrade my runtime until this is
fixed. (Sorry for the whining.)

-------------

11/4/99 test case received from user via email (jar file -- will test before pasting contents in here)

"java -cp TreeTest.jar TreeTest"

Reproducible with kestrel RA (1.3.0 build "I")...will file bug, and attach jar to the bug itself.

(Review ID: 97418)
======================================================================