-
Bug
-
Resolution: Duplicate
-
P1
-
None
-
1.1
-
generic
-
generic
Enabling (by setEnable) container which containes disabled components
doesn't effect such components and the label of those components still remains
grayed out on SOlaris but Windows.
On Windows enabling container results to change looking of components, those
looks like enabled but disabled in fact.
import java.awt.*;
import java.applet.*;
public class Flush2 extends Applet {
Choice choice1;
public void init() {
Button b = new Button("B") ;
add (choice1 = new Choice ());
add (b) ;
choice1.addItem (" black ");
b.setEnabled(true) ;
choice1.setEnabled(true) ;
this.setEnabled(false) ;
}
public boolean handleEvent(Event evt) {
if (evt.id == Event.ACTION_EVENT && evt.target instanceof Button) {
System.out.println("action!") ;
}
return true ;
}
}
doesn't effect such components and the label of those components still remains
grayed out on SOlaris but Windows.
On Windows enabling container results to change looking of components, those
looks like enabled but disabled in fact.
import java.awt.*;
import java.applet.*;
public class Flush2 extends Applet {
Choice choice1;
public void init() {
Button b = new Button("B") ;
add (choice1 = new Choice ());
add (b) ;
choice1.addItem (" black ");
b.setEnabled(true) ;
choice1.setEnabled(true) ;
this.setEnabled(false) ;
}
public boolean handleEvent(Event evt) {
if (evt.id == Event.ACTION_EVENT && evt.target instanceof Button) {
System.out.println("action!") ;
}
return true ;
}
}
- duplicates
-
JDK-1257395 disabling a container should recursively disable its child components
-
- Closed
-