Bug ID: 6683775 Painting artifacts is seen when panel is made setOpaque(false) for a translucent window

6683775 : Painting artifacts is seen when panel is made setOpaque(false) for a translucent window

Details

Type:	Bug	Submit Date:	2008-04-03
Status:	Closed	Updated Date:	2011-01-19
Project Name:	JDK	Resolved Date:	2009-05-18
Component:	client-libs	OS:	windows_xp
Sub-Component:	javax.swing	CPU:	x86
Priority:	P2
Resolution:	Fixed
Affected Versions:	6u10
Fixed Versions:	6u14

Related Reports

Backport:	JDK-2178127 - Painting artifacts is seen when panel is made setOpaque(false) for a translucent window
Relates:	JDK-6794764 - Translucent windows are completely repainted on every paint event, on Windows
Relates:	JDK-6668436 - Painting a component to an off-screen image should not affect the double buffer
Relates:	JDK-6848852 - PIT:test/javax/swing/JComponent/6683775/bug6683775.java on linux with RuntimeException.

Sub Tasks

Description

I have a frame , which is having a jpanel in the north & jpanel is having a button . In the center of the frame i have added a Jscrollpane which holds a textarea. I called panel.setOpaque(false) & set the frame to become translucent by calling  com.sun.awt.AWTUtilities.setWindowOpaque(frame, false); , when i call this method i can see two  button . I have attached screen shot of the same. When i comment the  com.sun.awt.AWTUtilities.setWindowOpaque(frame, false); line , Every thing works as expected. 

Step to reproduce:-
----------------------
1) Run the attached testcase.
2) If you see two button to the north of the frame , then the bug is reproduced.
Or see screen shot. If the gui & screen is seen then the bug is reproduce.


I run this program on 6u10 b14 .

Comments

EVALUATION This bug is reopened, we need to fix it the way that painting double-buffered components to an off-screen image not corrupt Swing double-buffer
2008-12-30
EVALUATION The idea of the fix is to paint through RepaintManager only if the paint() method is called by the Swing painting system (by RepaintManager itself or paintImmediately())
2008-12-30
SUGGESTED FIX The panel containing the components should be: 1. non-opaque: JPanel.setOpaque(false); 2. non-double-buffered: JPanel.setDoubleBuffered(false); In this case everything works fine.
2008-04-04
EVALUATION This is because making the components non-opaque (using setOpaque(false)) is not sufficient. The panel should had been made non-double-buffered as well (using the setDoubleBuffered(false)). Currently the Swing team is fixing this issue. Please refer to the CR 6668436 for more details. As soon as this CR is fixed the problem should disappear. Thus I'm closing this CR as a duplicate of the 6668436.
2008-04-04

SELECT A COUNTRY/REGION
Africa Operation Argentina Australia Austria Bahrain Bangladesh Belgium & Luxembourg Belize Bhutan Bolivia Bosnia & Herzegovina Brasil Brunei Bulgaria Cambodia Canada - English Canada - French Chile China Colombia	Costa Rica Croatia Cyprus Czech Republic Denmark Ecuador Egypt Estonia Finland France Germany Greece Guatemala Honduras Hong Kong Hungary India Indonesia Iraq Ireland	Israel Italy Japan Jordan Kazakhstan Korea Kuwait Laos Latvia Lebanon Lithuania Malaysia Maldives Malta Mexico Moldova Nepal Netherlands New Zealand Nicaragua	Norway Oman Pakistan Panama Paraguay Peru Philippines Poland Portugal Puerto Rico Qatar Romania Russia Saudi Arabia Serbia & Montenegro Singapore Slovakia Slovenia South Africa Spain	Sri Lanka Sweden Switzerland -- French Switzerland -- German Taiwan Thailand Turkey Ukraine United Arab Emirates United Kingdom United States Uruguay Venezuela Vietnam Yemen

Hardware and Software, Engineered to Work Together