JDK-4742412 : X11: Frames cannot be shown initially maximized
- Type: Bug
- Component: client-libs
- Sub-Component: java.awt
- Affected Version: 1.4.0
- Priority: P4
- Status: Closed
- Resolution: Cannot Reproduce
- OS: solaris_8
- CPU: sparc
- Submitted: 2002-09-05
- Updated: 2007-05-28
- Resolved: 2007-05-28
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.
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 7 |
|---|
7Resolved  |
Related Reports
|
Relates :
|
Description
Java version: 1.4.0
Frames cannot be shown initially maximized due to inset calculation/resize
dance (this makes Window Manager think that after maximization, another resize
happened). There was a similar bug filed against Windows platform (4464714), but
it was caused by different reasons, and is now fixed.
Test case:
===
import javax.swing.*;
public class Maxim extends JFrame
{
public static void main(String args[])
{
new Maxim();
}
public Maxim()
{
setDefaultCloseOperation(EXIT_ON_CLOSE);
setExtendedState(MAXIMIZED_BOTH);
show();
}
}
===
Comments
|