JDK-4452373 : display change on win32 not propagating to all heavyweight components
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 1.4.0
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_nt
  • CPU: x86
  • Submitted: 2001-04-30
  • Updated: 2001-05-22
  • Resolved: 2001-05-22
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.4.0 beta2Fixed
Related Reports
Relates :  
Relates :  
Description
On win32, it is necessary to send the display change event to all heaveyweight
components and offscreen images, to make sure that any display-dependent
data they have (such as the internal surface data objects) are updated with
the new display information.

In the latest 1.4 code, the display change is not being propagated
correctly and ends up missing some embedded heavyweight components.

For example, an application that embeds a heaveyweight component
(for example, a Canvas) in the contentPane of a JFrame will not 
be updated properly.

This problem can have indeterminate side effects, such as screen garbage
or application crashes due to bad memory references.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: merlin-beta2 FIXED IN: merlin-beta2 INTEGRATED IN: merlin-beta2
14-06-2004

EVALUATION AwtPanelPeer.displayChange() needs to recurse into any Container() children (which need to recurse into any Containers() there, etc.). This will propagate the event into any heavyweight which does not happen to lives at the top of the containment hierarchy. Fix implemented and appears to work. chet.haase@Eng 2001-04-30
30-04-2001