United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: 4905270 Side effect of sun.awt.noerasebackground=true workaround
4905270 : Side effect of sun.awt.noerasebackground=true workaround

Details
Type:
Bug
Submit Date:
2003-08-12
Status:
Resolved
Updated Date:
2003-11-15
Project Name:
JDK
Resolved Date:
2003-11-15
Component:
client-libs
OS:
windows_2000
Sub-Component:
java.awt
CPU:
x86
Priority:
P2
Resolution:
Fixed
Affected Versions:
1.4.0_01
Fixed Versions:
1.4.2_04

Related Reports
Backport:
JDK-2073300 - Side effect of sun.awt.noerasebackground=true workaround
Relates:
JDK-4881422 - repaint causes problems on multi-head configuration
Relates:
JDK-4959178 - Regression test fails for 4905270: Side effect of sun.awt.noerasebackground=true

Sub Tasks

Description
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.

Comments
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
2004-06-14 
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
2003-10-21


Hardware and Software, Engineered to Work Together