JDK-5025858 : Resizing a decorated frame triggers componentResized event twice.
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_9
  • CPU: sparc
  • Submitted: 2004-04-02
  • Updated: 2005-09-07
  • Resolved: 2005-09-07
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.
JDK 6
6 b51Fixed
Related Reports
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Description
Bug Description:
----------------
Resizing a decorated frame using setSize method triggers componentResized event twice.This doesn't happen in windows.

JDK-INFO:
---------
java version "1.5.0-beta2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-beta2-b43)
Java HotSpot(TM) Client VM (build 1.5.0-beta2-b43, mixed mode)

SYSTEM-INFO:
------------
SunOS aparup.india.sun.com 5.9 sun4u sparc 
 
BUILD-LOCATION:
---------------
/net/sqindia.india.sun.com/export/disk09/jdk/1.5.0/beta2/b43/binaries


Steps to Reproduce -
-------------------
1. Compile the file that is attached with this bug.
2. Now Execute, the componentResized event should be triggered twice. 

###@###.### 2004-04-02

Comments
SUGGESTED FIX http://sa.sfbay.sun.com/projects/awt_data/mustang/5025858/
2005-11-10

EVALUATION Name: rpR10076 Date: 04/02/2004 We might want to find out why the system sends us so many resize events. The problem doesn't look critical for tiger, though. ###@###.### ====================================================================== Name: dmR10075 Date: 04/02/2004 One of the events is generated right in Component.java, it is necessary to handle lightweight components. But for heavyweight peers it is probably not necessary since native systems generates events by itself. Since we do postEvent, we can probably change this code to generate events for lightweight components, and don't generate for heavyweight assuming native system will generate them later. ###@###.### 2004-04-02 ====================================================================== Might be considered performance related, since each COMPONENT_RESIZED event on toplevel causes validate() ###@###.### 2005-05-26 11:40:52 GMT
2005-05-26

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mustang
2004-09-07