JDK-4905270 : Side effect of sun.awt.noerasebackground=true workaround
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 1.4.0_01
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2003-08-12
  • Updated: 2003-11-15
  • Resolved: 2003-11-15
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.
1.4.2_04 04Fixed
Related Reports
Relates :  
Relates :  
Customer is using the flag "sun.awt.noerasebackground=true" to overcome a repaing bug (id # 4881422). But they see a side effect due to this in that
during the process of resizing the window, there is a new repaint problem.

The attached snapshot shows the effect of this bug. The image repaints itself
after the window is resized and the mouse button is released.

The problem is also seen only when the "Show window contents while dragging" option in " Control Panel -> Display -> Effects" is turned on.

The application can be used in "fixed mode" and "floating mode". In fixed mode:

a. The inner frames are JInterFrames which are lightweight objects and outer
   frames is a heavy weight component.

b. The new repaint problem is seen only while resizing the outer window.

In floating mode:

a. All the windows become JFrames.

b. The repaint prolbem is seen while resizing all the windows.

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.4.2_04 tiger-beta FIXED IN: 1.4.2_04 tiger-beta INTEGRATED IN: 1.4.2_04 tiger-beta

EVALUATION Sounds like a high-impact bug (likely escalation): should address for Tiger. ###@###.### 2003-08-12 I sent email to the submitter to get more info on how to reproduce the problem. Looks like it needs a multimonitor setup which I dont have. ###@###.### 2003-10-01 Ok, now I understand that they are complaining about the fact that you see dirty regions when you specify sun.awt.noerasebackground=true and have dynamic layout enabled in the OS. Unfortunately this is correct behaviour. Specifying sun.awt.noerasebackground=true tells AWT not to erase the background for exposed regions. So on a dynamic layout environment, you WILL see the dirty regions. This is exactly what sun.awt.noerasebackground=true specifies. So this is not a bug. The problem here is that the customer is forced to use this because of 4881422. So the only way to solve this problem is to fix 4881422. I am closing this case as not a bug. ###@###.### 2003-10-02 CTE has proposed a fix to add another property to disable the noerasebackground property while resizing therefore avoiding the above mentioned side effect. ###@###.### 2003-10-21