-
Bug
-
Resolution: Duplicate
-
P3
-
None
-
1.1
-
generic, x86, sparc
-
solaris_2.5.1, solaris_10, windows_95
Item events are not properly generated when the state of a Checkbox or List is
changed programmatically.
###@###.### 1999-07-06
I have to come up with this again, as we (Compatibility Kits team) cannot have
bug ids closed as not a bug on the exclude list.
Could someone explain why this is not a bug? JDC docs state:
'When an item is selected or deselected, AWT sends an instance of
ItemEvent to the list' JCK tests expect ItemEvents to be generated,
and they fail.
I'm reopening this bug with hope that someone will address this.
----------------------------------------------------------------------
By doing a setState() there's no ItemEvent generated. Is this the intent
of the design? If so the doc will have to be change to explicitly state
this behavior.
Roger Pham 3/7/2000
changed programmatically.
###@###.### 1999-07-06
I have to come up with this again, as we (Compatibility Kits team) cannot have
bug ids closed as not a bug on the exclude list.
Could someone explain why this is not a bug? JDC docs state:
'When an item is selected or deselected, AWT sends an instance of
ItemEvent to the list' JCK tests expect ItemEvents to be generated,
and they fail.
I'm reopening this bug with hope that someone will address this.
----------------------------------------------------------------------
By doing a setState() there's no ItemEvent generated. Is this the intent
of the design? If so the doc will have to be change to explicitly state
this behavior.
Roger Pham 3/7/2000
- duplicates
-
JDK-4034837 Checkbox.setState() does not notify listeners
-
- Closed
-
-
JDK-4318851 ItemEvent not triggered List,Choice,CheckBox,CheckboxMenuItem
-
- Closed
-